[JBoss JIRA] Created: (SEAM-94) Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions)
12:16 p.m.
Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the
same classes twice in the classpath (possibly different versions)
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SEAM-94
URL: https://issues.jboss.org/browse/SEAM-94
Project: Seam 3 Distribution
Issue Type: Bug
Reporter: Geoffrey De Smet
Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935.
Trying to avoid the shaded jars, is impossible, as this example shows:
{code}
$ mvn dependency:tree
...
[INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========> my
compile dependency on solder-api (the non-shaded jar)
[INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========> my
runtime dependency on solder-impl (the non-shaded jar)
[INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile
...
[INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile
[INFO] | +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============>
transitive dependency on solder (the shaded jar) which shades the classes of solder-api
{code}
Now suppose I depend on solder-api 3.0..Final instead (still with seam-security-impl
3.0.0.Final): I 'd have 2 different versions of solder in my classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:22 p.m.
New subject: [JBoss JIRA] Updated: (SEAM-94) Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions)
[
https://issues.jboss.org/browse/SEAM-94?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet updated SEAM-94:
---------------------------------
Description:
Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935.
Trying to avoid the shaded jars, is impossible, as this example shows:
{code}
$ mvn dependency:tree
...
[INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========> my
compile dependency on solder-api (the non-shaded jar)
[INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========> my
runtime dependency on solder-impl (the non-shaded jar)
[INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile
...
[INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile
[INFO] | +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============>
transitive dependency on solder (the shaded jar) which shades the classes of solder-api
{code}
Now suppose I depend on solder-api 3.0.1.Final instead (still with seam-security-impl
3.0.0.Final): I 'd have 2 different versions of solder in my classpath.
was:
Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935.
Trying to avoid the shaded jars, is impossible, as this example shows:
{code}
$ mvn dependency:tree
...
[INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========> my
compile dependency on solder-api (the non-shaded jar)
[INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========> my
runtime dependency on solder-impl (the non-shaded jar)
[INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile
...
[INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile
[INFO] | +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============>
transitive dependency on solder (the shaded jar) which shades the classes of solder-api
{code}
Now suppose I depend on solder-api 3.0..Final instead (still with seam-security-impl
3.0.0.Final): I 'd have 2 different versions of solder in my classpath.
Shaded jars like seam-solder instead of seam-solder-api and
seam-solder-impl result in the same classes twice in the classpath (possibly different
versions)
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SEAM-94
URL: https://issues.jboss.org/browse/SEAM-94
Project: Seam 3 Distribution
Issue Type: Bug
Reporter: Geoffrey De Smet
Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935.
Trying to avoid the shaded jars, is impossible, as this example shows:
{code}
$ mvn dependency:tree
...
[INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========>
my compile dependency on solder-api (the non-shaded jar)
[INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========>
my runtime dependency on solder-impl (the non-shaded jar)
[INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile
...
[INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile
[INFO] | +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============>
transitive dependency on solder (the shaded jar) which shades the classes of solder-api
{code}
Now suppose I depend on solder-api 3.0.1.Final instead (still with seam-security-impl
3.0.0.Final): I 'd have 2 different versions of solder in my classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:33 p.m.
New subject: [JBoss JIRA] Commented: (SEAM-94) Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions)
[
https://issues.jboss.org/browse/SEAM-94?page=com.atlassian.jira.plugin.sy...
]
Shane Bryzak commented on SEAM-94:
----------------------------------
Shaded jars are going away in Seam 3.1.
Shaded jars like seam-solder instead of seam-solder-api and
seam-solder-impl result in the same classes twice in the classpath (possibly different
versions)
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SEAM-94
URL: https://issues.jboss.org/browse/SEAM-94
Project: Seam 3 Distribution
Issue Type: Bug
Reporter: Geoffrey De Smet
Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935.
Trying to avoid the shaded jars, is impossible, as this example shows:
{code}
$ mvn dependency:tree
...
[INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========>
my compile dependency on solder-api (the non-shaded jar)
[INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========>
my runtime dependency on solder-impl (the non-shaded jar)
[INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile
...
[INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile
[INFO] | +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============>
transitive dependency on solder (the shaded jar) which shades the classes of solder-api
{code}
Now suppose I depend on solder-api 3.0.1.Final instead (still with seam-security-impl
3.0.0.Final): I 'd have 2 different versions of solder in my classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:35 p.m.
New subject: [JBoss JIRA] Commented: (SEAM-94) Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions)
[
https://issues.jboss.org/browse/SEAM-94?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet commented on SEAM-94:
--------------------------------------
Woohow! I 'll dance on their grave :)
Shaded jars like seam-solder instead of seam-solder-api and
seam-solder-impl result in the same classes twice in the classpath (possibly different
versions)
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SEAM-94
URL: https://issues.jboss.org/browse/SEAM-94
Project: Seam 3 Distribution
Issue Type: Bug
Reporter: Geoffrey De Smet
Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935.
Trying to avoid the shaded jars, is impossible, as this example shows:
{code}
$ mvn dependency:tree
...
[INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========>
my compile dependency on solder-api (the non-shaded jar)
[INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========>
my runtime dependency on solder-impl (the non-shaded jar)
[INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile
...
[INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile
[INFO] | +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============>
transitive dependency on solder (the shaded jar) which shades the classes of solder-api
{code}
Now suppose I depend on solder-api 3.0.1.Final instead (still with seam-security-impl
3.0.0.Final): I 'd have 2 different versions of solder in my classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:37 p.m.
New subject: [JBoss JIRA] (SEAM-94) Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions)
[
https://issues.jboss.org/browse/SEAM-94?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet resolved SEAM-94.
----------------------------------
Fix Version/s: 3.1.0.Beta3
Resolution: Done
3.1.0.Beta2 fixed this.
Shaded jars like seam-solder instead of seam-solder-api and
seam-solder-impl result in the same classes twice in the classpath (possibly different
versions)
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SEAM-94
URL: https://issues.jboss.org/browse/SEAM-94
Project: Seam 3 Distribution
Issue Type: Bug
Reporter: Geoffrey De Smet
Fix For: 3.1.0.Beta3
Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935.
Trying to avoid the shaded jars, is impossible, as this example shows:
{code}
$ mvn dependency:tree
...
[INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========>
my compile dependency on solder-api (the non-shaded jar)
[INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========>
my runtime dependency on solder-impl (the non-shaded jar)
[INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile
...
[INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile
[INFO] | +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============>
transitive dependency on solder (the shaded jar) which shades the classes of solder-api
{code}
Now suppose I depend on solder-api 3.0.1.Final instead (still with seam-security-impl
3.0.0.Final): I 'd have 2 different versions of solder in my classpath.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4641
days inactive
4729
days old
4 comments
3 participants
participants (3)
-
Geoffrey De Smet (JIRA) -
Geoffrey De Smet (Resolved) (JIRA)
-
Shane Bryzak (JIRA)