6:44 a.m.
Latest ejb3 artifacts contain a weird ejb3 client library.
I guess this should be named jboss-ejb3-client.jar?
/Heiko
7:20 a.m.
This artifact is a subset of the EJB3 Core project, and is generated by
the Maven assembly plugin as part of the build lifecycle. The resultant
name is due to the Maven convention [projectName]-[assemblyId]-[packaging].
S,
ALR
Heiko Braun wrote:
Latest ejb3 artifacts contain a weird ejb3 client library.
I guess this should be named jboss-ejb3-client.jar?
/Heiko
7:46 a.m.
...not that my explanation answers your question as to whether it should
be renamed, just some context.
If I can figure how to override Maven's default assignment in under a
day's work, I think this is a worthy change. ;) The EJB3 Client JAR
won't be restricted to code located in Core anyway.
http://jira.jboss.com/jira/browse/EJBTHREE-1210
S,
ALR
Andrew Lee Rubinger wrote:
This artifact is a subset of the EJB3 Core project, and is generated
by
the Maven assembly plugin as part of the build lifecycle. The resultant
name is due to the Maven convention [projectName]-[assemblyId]-[packaging].
S,
ALR
Heiko Braun wrote:
> Latest ejb3 artifacts contain a weird ejb3 client library.
> I guess this should be named jboss-ejb3-client.jar?
>
> /Heiko
>
8:05 a.m.
Right, that was my question.
It currently breaks each ejb3 client classpath,
that used to work with the former notion.
"If I can figure how to override Maven's default assignment in under a
day's work, I think this is a worthy change."
Well, if it takes you more time then writing this email you should
consider using a different build environment.
/Heiko
On Mon, 2008-03-10 at 08:46 -0400, Andrew Lee Rubinger wrote:
...not that my explanation answers your question as to whether it
should
be renamed, just some context.
8:18 a.m.
Heiko Braun wrote:
Right, that was my question.
It currently breaks each ejb3 client classpath,
that used to work with the former notion.
Would you please comment on the JIRA with some specifics? What's
missing / giving CNFEs?
"If I can figure how to override Maven's default assignment
in under a
day's work, I think this is a worthy change."
Well, if it takes you more time then writing this email you should
consider using a different build environment.
Maven's odd that way. You don't spend 5 days writing dependency
management, but you do spend 4 hours changing a filename. Even with all
the frustrations in Mavenizing, I prefer over Ant scripts any day.
S,
ALR
6206
days inactive
6206
days old
jboss-development@lists.jboss.org
5 comments
2 participants
participants (2)
-
Andrew Lee Rubinger -
Heiko Braun