Changelog cvs problems
Hi, I am desperately trying to get the Changelog to work, for 2 days now. I'm running Windows 2000 SP4, CVSNT, CVS 1.11.15, Maven v. 1.0-rc2. Conn. string: repository developerConnectionscm|cvs|pserver|[EMAIL PROTECTED]|C:/OSO/cvsrepo/test| Sample_project2/developerConnection /repository Result: [echo] Generating the Change Log... maven-changelog-plugin:report: [echo] Generating the changelog report Didn't find password for CVSROOT ':pserver:[EMAIL PROTECTED]:C:/OSO/cvsrepo/test'. org.netbeans.lib.cvsclient.connection.AuthenticationException: Wrong Password. ChangeLog found: 0 entries I tried first logging in to CVS, but that didn't help - also I tried both with the auto-generated .cvspass and with the /1 deleted (see http://jira.codehaus.org/ViewIssue.jspa?key=MPCHANGELOG-34) I'm afraid I'm overlooking something really simple, but I just don't see it. Any help appreciated, Mylène This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Changelog cvs problems
Using : as a separator does not play nicely with drive letters. -Original Message- From: Arto Pastinen [mailto:[EMAIL PROTECTED] Sent: 22 April 2004 12:12 To: Maven Users List Subject: Re: Changelog cvs problems Hi! Did you miss Menetrieux's reply this today? Here it is: Why you do use : as separator ?? Why you don't use an other separator ? I'm under linux too and this works fine: You see that the ':' separator is use for separate username and passwd.. connectionscm|cvs|pserver|username:[EMAIL PROTECTED]|repository| module/connec tion Actually i didn't test it, i added anonymous access to CVS, but try it, i think that it can help. On Thu, 2004-04-22 at 13:59, Mylene Reiners wrote: Hi, I am desperately trying to get the Changelog to work, for 2 days now. I'm running Windows 2000 SP4, CVSNT, CVS 1.11.15, Maven v. 1.0-rc2. Conn. string: repository developerConnectionscm|cvs|pserver|[EMAIL PROTECTED]|C:/OSO /cvsrepo/test| Sample_project2/developerConnection /repository Result: [echo] Generating the Change Log... maven-changelog-plugin:report: [echo] Generating the changelog report Didn't find password for CVSROOT ':pserver:[EMAIL PROTECTED]:C:/OSO/cvsrepo/test'. org.netbeans.lib.cvsclient.connection.AuthenticationException: Wrong Password. ChangeLog found: 0 entries I tried first logging in to CVS, but that didn't help - also I tried both with the auto-generated .cvspass and with the /1 deleted (see http://jira.codehaus.org/ViewIssue.jspa?key=MPCHANGELOG-34) I'm afraid I'm overlooking something really simple, but I just don't see it. Any help appreciated, Mylène This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Changelog cvs problems
Yes, and actually doesn't xml spec's has something to say about those '/' characters.. =) don't remember character english name.. On Thu, 2004-04-22 at 14:09, Peter Bright wrote: Using : as a separator does not play nicely with drive letters. -Original Message- From: Arto Pastinen [mailto:[EMAIL PROTECTED] Sent: 22 April 2004 12:12 To: Maven Users List Subject: Re: Changelog cvs problems Hi! Did you miss Menetrieux's reply this today? Here it is: Why you do use : as separator ?? Why you don't use an other separator ? I'm under linux too and this works fine: You see that the ':' separator is use for separate username and passwd.. connectionscm|cvs|pserver|username:[EMAIL PROTECTED]|repository| module/connec tion Actually i didn't test it, i added anonymous access to CVS, but try it, i think that it can help. On Thu, 2004-04-22 at 13:59, Mylene Reiners wrote: Hi, I am desperately trying to get the Changelog to work, for 2 days now. I'm running Windows 2000 SP4, CVSNT, CVS 1.11.15, Maven v. 1.0-rc2. Conn. string: repository developerConnectionscm|cvs|pserver|[EMAIL PROTECTED]|C:/OSO /cvsrepo/test| Sample_project2/developerConnection /repository Result: [echo] Generating the Change Log... maven-changelog-plugin:report: [echo] Generating the changelog report Didn't find password for CVSROOT ':pserver:[EMAIL PROTECTED]:C:/OSO/cvsrepo/test'. org.netbeans.lib.cvsclient.connection.AuthenticationException: Wrong Password. ChangeLog found: 0 entries I tried first logging in to CVS, but that didn't help - also I tried both with the auto-generated .cvspass and with the /1 deleted (see http://jira.codehaus.org/ViewIssue.jspa?key=MPCHANGELOG-34) I'm afraid I'm overlooking something really simple, but I just don't see it. Any help appreciated, Mylène This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Changelog cvs problems
Er... that wasn't meant to happen. What I meant to say was, did you try sticking a password into the connection string? -Original Message- From: Peter Bright [mailto:[EMAIL PROTECTED] Sent: 22 April 2004 12:10 To: 'Maven Users List' Subject: RE: Changelog cvs problems Using : as a separator does not play nicely with drive letters. -Original Message- From: Arto Pastinen [mailto:[EMAIL PROTECTED] Sent: 22 April 2004 12:12 To: Maven Users List Subject: Re: Changelog cvs problems Hi! Did you miss Menetrieux's reply this today? Here it is: Why you do use : as separator ?? Why you don't use an other separator ? I'm under linux too and this works fine: You see that the ':' separator is use for separate username and passwd.. connectionscm|cvs|pserver|username:[EMAIL PROTECTED]|repository| module/connec tion Actually i didn't test it, i added anonymous access to CVS, but try it, i think that it can help. On Thu, 2004-04-22 at 13:59, Mylene Reiners wrote: Hi, I am desperately trying to get the Changelog to work, for 2 days now. I'm running Windows 2000 SP4, CVSNT, CVS 1.11.15, Maven v. 1.0-rc2. Conn. string: repository developerConnectionscm|cvs|pserver|[EMAIL PROTECTED]|C:/OSO /cvsrepo/test| Sample_project2/developerConnection /repository Result: [echo] Generating the Change Log... maven-changelog-plugin:report: [echo] Generating the changelog report Didn't find password for CVSROOT ':pserver:[EMAIL PROTECTED]:C:/OSO/cvsrepo/test'. org.netbeans.lib.cvsclient.connection.AuthenticationException: Wrong Password. ChangeLog found: 0 entries I tried first logging in to CVS, but that didn't help - also I tried both with the auto-generated .cvspass and with the /1 deleted (see http://jira.codehaus.org/ViewIssue.jspa?key=MPCHANGELOG-34) I'm afraid I'm overlooking something really simple, but I just don't see it. Any help appreciated, Mylène This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Changelog cvs problems
Well, without them I can't get it to work on windows, because of the c:\ drive I have to define. The usual : delimiter is therefore changed in | But Arto's (or Menetrieux) solution worked. The username and password have to be divided by : It works with the connection string repository developerConnectionscm|cvs|pserver|MReiners:[EMAIL PROTECTED]|C:/OSO/cvsr epo/test|Sample_project2/developerConnection /repository Thanks a lot, Mylene -Original Message- From: Peter Bright [mailto:[EMAIL PROTECTED] Sent: 22 April 2004 13:10 To: 'Maven Users List' Subject: RE: Changelog cvs problems Using : as a separator does not play nicely with drive letters. -Original Message- From: Arto Pastinen [mailto:[EMAIL PROTECTED] Sent: 22 April 2004 12:12 To: Maven Users List Subject: Re: Changelog cvs problems Hi! Did you miss Menetrieux's reply this today? Here it is: Why you do use : as separator ?? Why you don't use an other separator ? I'm under linux too and this works fine: You see that the ':' separator is use for separate username and passwd.. connectionscm|cvs|pserver|username:[EMAIL PROTECTED]|repository| module/connec tion Actually i didn't test it, i added anonymous access to CVS, but try it, i think that it can help. On Thu, 2004-04-22 at 13:59, Mylene Reiners wrote: Hi, I am desperately trying to get the Changelog to work, for 2 days now. I'm running Windows 2000 SP4, CVSNT, CVS 1.11.15, Maven v. 1.0-rc2. Conn. string: repository developerConnectionscm|cvs|pserver|[EMAIL PROTECTED]|C:/OSO /cvsrepo/test| Sample_project2/developerConnection /repository Result: [echo] Generating the Change Log... maven-changelog-plugin:report: [echo] Generating the changelog report Didn't find password for CVSROOT ':pserver:[EMAIL PROTECTED]:C:/OSO/cvsrepo/test'. org.netbeans.lib.cvsclient.connection.AuthenticationException: Wrong Password. ChangeLog found: 0 entries I tried first logging in to CVS, but that didn't help - also I tried both with the auto-generated .cvspass and with the /1 deleted (see http://jira.codehaus.org/ViewIssue.jspa?key=MPCHANGELOG-34) I'm afraid I'm overlooking something really simple, but I just don't see it. Any help appreciated, Mylène This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: aspectj plugin maven 1.0 rc2
That line is mandatory
-Mensaje original-
De: Daniel Henrique Alves Lima [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 22 de abril de 2004 0:11
Para: Maven Users List
Asunto: Re: aspectj plugin maven 1.0 rc2
I've added the following line in my project.xml and the error
seems to stop :
aspectSourceDirectorysrc/java/aspectSourceDirectory
Daniel Henrique Alves Lima wrote:
Now i'm getting this already defined message for all
my classes...
Can be a configuration problem ? I don't have any aspectj plugin
property defined in my project.properties and i'm trying to
run maven
aspectj:compile or just maven aspectj.
[iajc] couldn't find aspectjrt.jar on classpath, checked:
[iajc] /projects/new_project/database/RowIterator.jav
a:14 The type RowIterator is already defined
[iajc] public interface RowIterator extends Iterator {
[iajc]
Vincent Massol wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: aspectj plugin maven 1.0 rc2
Yes, that's required. I guess we should add a check in the plugin to
verify it's defined. Maybe you could file a JIRA issue on the aspectj
plugin for this.
Thanks
-Vincent
-Original Message-
From: Daniel Henrique Alves Lima [mailto:[EMAIL PROTECTED]
Sent: 22 April 2004 00:11
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
I've added the following line in my project.xml and the error seems to
stop :
aspectSourceDirectorysrc/java/aspectSourceDirectory
Daniel Henrique Alves Lima wrote:
Now i'm getting this already defined message for all my
classes...
Can be a configuration problem ? I don't have any aspectj plugin
property defined in my project.properties and i'm trying to run
maven aspectj:compile or just maven aspectj.
[iajc] couldn't find aspectjrt.jar on classpath, checked:
[iajc] /projects/new_project/database/RowIterator.jav
a:14 The type RowIterator is already defined
[iajc] public interface RowIterator extends Iterator {
[iajc]
Vincent Massol wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven.xml and Prject.properties extension question
Hello, I am migrating my projects from ant to maven, and i've almost completed my task, but right now i am facing a last challenge. Basically i have 3 different kind of project.properties and maven.xml, that are always repeted. I'd like to know if there's a way to allow extension also for those 2 files, as for the property file i read somewhere about a util taks to import another file, but not sure where. For the Maven.xml i am using the entities but if i want to add a pregoal for example i need to manually edit all the files in my repository... that's about 30 each time i need to add a property or a goal. Thanks for your help Max - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DLLs as dependencies
I have a project that uses the wrapper.jar as one of its dependencies. However, along with the jar, there is also a wrapper.dll that is needed. Is there a way to specify the dll as a dependency as well? This would be useful for all projects using JNI. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DLLs as dependencies
dependency groupIdyour_group/groupId artifactIdwrapper/artifactId typedll/type /dependency And put your dll in $repo/your_group/dlls/wrapper.dll Emmanuel - Original Message - From: Arto Pastinen [EMAIL PROTECTED] To: Maven Users List [EMAIL PROTECTED] Sent: Thursday, April 22, 2004 2:31 PM Subject: Re: DLLs as dependencies .. and *.so also. ;) On Thu, 2004-04-22 at 15:22, David R Robison wrote: I have a project that uses the wrapper.jar as one of its dependencies. However, along with the jar, there is also a wrapper.dll that is needed. Is there a way to specify the dll as a dependency as well? This would be useful for all projects using JNI. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven XDoclet Plugin and the maven.xdoclet.ejbdoclet.fileset property
--- Webb Morris [EMAIL PROTECTED] wrote:
I've been thinking about what Konstantin said below:
And you always have option to use ant invokation for
xdoclet tasks un your maven.xml - this is prefererd
way for xdoclet 2 ( at least there is no maven
plugin
planned, because everything got easier )
It seems to me, that no matter how much easier
things got with the new XDoclet 2 way of doing
things, that wrapping up that functionality in a
plugin would still be preferable. That way, you
wouldn't have to keep writing the same snippet of
maven.xml over and over again for each project
that used XDoclet. Perhaps my ignorance of how easy
things in XDoclet 2 are going to be is at
fault here, but there are plugins available for
lot's of easy tasks (JAR for instance) that make
life much simpler.
That's my invocation of xdoclet 2 in maven:
---%---
goal name=xdoclet-all
path id=xdoclet.task.classpath
pathelement location=${basedir}/src/main/merge/
pathelement location=${basedir}/src/test//
path refid=maven.dependency.classpath/
/path
taskdef
name=xdoclet
classname=org.xdoclet.ant.XDocletTask
classpathref=xdoclet.task.classpath
/
xdoclet
fileset
dir=${pom.build.sourceDirectory}
include name=**/*.java/
/fileset
component
classname=org.xdoclet.plugin.hibernate.HibernateMappingPlugin
destdir=${basedir}/target/xdoclet/hibernatedoclet
/
component
classname=org.xdoclet.plugin.webwork.ViewsPropertiesPlugin
destdir=${basedir}/target/xdoclet/webdoclet
/
component
classname=org.xdoclet.plugin.externalizer.MessageBundlePlugin
destdir=${basedir}/target/xdoclet/xdoclet
/
component
classname=org.xdoclet.plugin.externalizer.PropertiesTranslatorPlugin
destdir=${basedir}/target/xdoclet/xdoclet
/
/xdoclet
path id=xdoclet.java.compile.src.set
location=${basedir}/target/xdoclet/xdoclet/
maven:addPath id=maven.compile.src.set
refid=xdoclet.java.compile.src.set/
/goal
---%
As you may see ( or not :) ) ant task for xdoclet-2
is basically a picocontainer, where you just drop
components you deem appropriate.
( and you may as well use several instances of same
task )
Yes, it's possible to wrap in plugin, but it would
require a lot of properties to set up
I prefer this way. Though taskdef part could be
factored out.
regards,
=
[ Konstantin Pribluda ( ko5tik ) ]
Zu Verstärkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] für die Festanstellung.
Arbeitsort: Mainz
Skills: Programieren, Kentnisse in OpenSource-Bereich
[ http://www.pribluda.de ]
__
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http://photos.yahoo.com/ph/print_splash
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: aspectj plugin maven 1.0 rc2
I agree that it should be added, I added a comment to my patch where I
suggested changing
aspectj.weavetrue/aspectj.weave
to
aspectj.weaveWithtrue/aspectj.weaveWith
so people don't confuse weawing with the aspects from a jar with weaving the
clases of a jar.
I think Vincent would appreciate if you post the patch in JIRA and document
it.
-Mensaje original-
De: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 22 de abril de 2004 18:11
Para: Maven Users List
Asunto: Re: aspectj plugin maven 1.0 rc2
A while back I inserted injars into my plugin.jelly file
for the aspecj plugin and its been going great. It gives me
the ability to weave an aspect into a pre-compiled jar. This
feature is available when using iajc so it is not something I made up.
Thing is, each time I upgrade or build from CVS I completely
forget that I had added it and my builds stop working. Is
there any way to get this added to the
maven-aspectj-plugin/plugin.jelly file permanently? It would
be part of the weave-internal task.
!-- Private goal used to that when the jar:jar postgoal is
called we don't
have to call aspectj:init and jar:jar twice --
goal name=aspectj:weave-internal
!-- fork to avoid BCEL library version conflict with
maven --
ant:iajc fork=true debug=${maven.aspectj.debug}
outjar=${maven.aspectj.outjar}
injars=${maven.aspectj.injar.nonweaved}
sourceRootCopyFilter=${maven.aspectj.sourceRootCopyFilters}
emacssym=${maven.aspectj.emacssym}
!-- Look for aspect libraries to weave into --
ant:injars
j:forEach var=artifact items=${pom.artifacts}
j:set var=dep value=${artifact.dependency}/
j:if test=${dep.getProperty('aspect.injar')=='true'}
ant:pathelement location=${artifact.path}/
/j:if
/j:forEach
/ant:injars
/ant:iajc
/goal
It would require jars that are being weaved into to have a
property defined in the project.xml. I have called this
property aspect.injar.
So:
dependency
groupIdmyjar/groupId
typejar/type
artifactIdmyjar/artifactId
version2.0/version
properties
aspect.injartrue/aspect.injar
/properties
/dependency
How 'bout it? Should I file this in JIRA? Is the mailing
list good enough?
Also, you can get rid of
copyInjars=true
from the ant:iajc task since it is no longer required by
aspectj-1.1.1.
Let me know your thoughts, I would really like to see this get added.
Thanks a lot.
Charlie
Vincent Massol wrote:
Yes, that's required. I guess we should add a check in the plugin to
verify it's defined. Maybe you could file a JIRA issue on
the aspectj
plugin for this.
Thanks
-Vincent
-Original Message-
From: Daniel Henrique Alves Lima
[mailto:[EMAIL PROTECTED]
Sent: 22 April 2004 00:11
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
I've added the following line in my project.xml and the
error seems to
stop :
aspectSourceDirectorysrc/java/aspectSourceDirectory
Daniel Henrique Alves Lima wrote:
Now i'm getting this already defined message for all my
classes...
Can be a configuration problem ? I don't have any
aspectj plugin
property defined in my project.properties and i'm trying to run
maven aspectj:compile or just maven aspectj.
[iajc] couldn't find aspectjrt.jar on classpath, checked:
[iajc] /projects/new_project/database/RowIterator.jav
a:14 The type RowIterator is already defined
[iajc] public interface RowIterator extends Iterator {
[iajc]
Vincent Massol wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: aspectj plugin maven 1.0 rc2
Hi Charles / Carlos,
Carlos has sent a big patch a few days back. I'm still fighting to find
some time to read it, analyze it and decide whether we should apply it
as is or with some tweaks (I think we agree to remove the autoweave
feature for example). There are several parameters that come into
account, one of them being the fact that the new version of AspectJ
supports weaving aspects into directories (and not only jars).
Anyway, I have to admit I am a bit overwhelmed and would appreciate help
on this. If Carlos and you could talk this over and jointly submit a
patch that satisfies everyone (possibly using the latest version of
AspectJ), it would help tremendously. The patch should also include
updates to xdocs and the changes.xml file.
Many thanks
-Vincent
-Original Message-
From: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Sent: 22 April 2004 18:11
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
A while back I inserted injars into my plugin.jelly file for the
aspecj
plugin and its been going great. It gives me the ability to weave an
aspect into a pre-compiled jar. This feature is available when using
iajc
so it is not something I made up.
Thing is, each time I upgrade or build from CVS I completely forget
that
I had added it and my builds stop working. Is there any way to get
this
added to the maven-aspectj-plugin/plugin.jelly file permanently? It
would
be part of the weave-internal task.
!-- Private goal used to that when the jar:jar postgoal is called
we
don't
have to call aspectj:init and jar:jar twice --
goal name=aspectj:weave-internal
!-- fork to avoid BCEL library version conflict with maven
--
ant:iajc fork=true debug=${maven.aspectj.debug}
outjar=${maven.aspectj.outjar}
injars=${maven.aspectj.injar.nonweaved}
sourceRootCopyFilter=${maven.aspectj.sourceRootCopyFilters}
emacssym=${maven.aspectj.emacssym}
!-- Look for aspect libraries to weave into --
ant:injars
j:forEach var=artifact items=${pom.artifacts}
j:set var=dep value=${artifact.dependency}/
j:if test=${dep.getProperty('aspect.injar')=='true'}
ant:pathelement location=${artifact.path}/
/j:if
/j:forEach
/ant:injars
/ant:iajc
/goal
It would require jars that are being weaved into to have a property
defined in the project.xml. I have called this property
aspect.injar.
So:
dependency
groupIdmyjar/groupId
typejar/type
artifactIdmyjar/artifactId
version2.0/version
properties
aspect.injartrue/aspect.injar
/properties
/dependency
How 'bout it? Should I file this in JIRA? Is the mailing list good
enough?
Also, you can get rid of
copyInjars=true
from the ant:iajc task since it is no longer required by
aspectj-1.1.1.
Let me know your thoughts, I would really like to see this get added.
Thanks a lot.
Charlie
Vincent Massol wrote:
Yes, that's required. I guess we should add a check in the plugin to
verify it's defined. Maybe you could file a JIRA issue on the aspectj
plugin for this.
Thanks
-Vincent
-Original Message-
From: Daniel Henrique Alves Lima
[mailto:[EMAIL PROTECTED]
Sent: 22 April 2004 00:11
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
I've added the following line in my project.xml and the error seems
to
stop :
aspectSourceDirectorysrc/java/aspectSourceDirectory
Daniel Henrique Alves Lima wrote:
Now i'm getting this already defined message for all my
classes...
Can be a configuration problem ? I don't have any aspectj plugin
property defined in my project.properties and i'm trying to run
maven aspectj:compile or just maven aspectj.
[iajc] couldn't find aspectjrt.jar on classpath, checked:
[iajc] /projects/new_project/database/RowIterator.jav
a:14 The type RowIterator is already defined
[iajc] public interface RowIterator extends Iterator {
[iajc]
Vincent Massol wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven was5 plugin deploy problem
i'm getting the following error when trying to deploy to my local websphere server with the was5 plugin. i am generating the xmi files with xdoclet, why can't it find the jndi name in the config file? - [wasInstallApp] WASX7017E: Exception received while running file /tmp/wsant46022jacl; exception information: com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task BindJndiForEJBNonMessageBinding [wasInstallApp] [wasInstallApp] ADMA0002E: Validation error in task Binding Enterprise Beans to JNDI Names [wasInstallApp] JNDI name is not specified for EJB CommandServer in module Generated by XDoclet. [wasInstallApp] [wasInstallApp] [ERROR] Java Result: 105 - ejbbnd:EJBJarBinding xmi:version=2.0 xmlns:xmi=http://www.omg.org/XMI; http://www.omg.org/XMI%22; xmlns:ejbbnd=ejbbnd.xmi xmlns:ejb=ejb.xmi xmlns:commonbnd=commonbnd.xmi xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; http://www.w3.org/2001/XMLSchema-instance%22; xmi:id=ejb-jar_ID_Bnd ejbJar href=META-INF/ejb-jar.xml#ejb-jar_1/ ejbBindings xmi:id=Session_bnd_1 jndiName=ejb/CommandServer enterpriseBean xmi:type=ejb:Session href=META-INF/ejb-jar.xml#Session_CommandServer / /ejbBindings /ejbbnd:EJBJarBinding - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: aspectj plugin maven 1.0 rc2
Charles,
Can you apply the patch I've made (
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPASPECTJ-8 ) and then
change aspectj:weave-internal and the xdocs to reflect your changes and
submit it again to Jira?
I think the only thing we should think about are the name of the dependency
properties. I had though about aspectj.weave and aspectj.weaveWith but,
what do you think?
-Mensaje original-
De: Vincent Massol [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 22 de abril de 2004 18:22
Para: 'Maven Users List'
CC: [EMAIL PROTECTED]
Asunto: RE: aspectj plugin maven 1.0 rc2
Hi Charles / Carlos,
Carlos has sent a big patch a few days back. I'm still
fighting to find some time to read it, analyze it and decide
whether we should apply it as is or with some tweaks (I think
we agree to remove the autoweave feature for example). There
are several parameters that come into account, one of them
being the fact that the new version of AspectJ supports
weaving aspects into directories (and not only jars).
Anyway, I have to admit I am a bit overwhelmed and would
appreciate help on this. If Carlos and you could talk this
over and jointly submit a patch that satisfies everyone
(possibly using the latest version of AspectJ), it would help
tremendously. The patch should also include updates to xdocs
and the changes.xml file.
Many thanks
-Vincent
-Original Message-
From: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Sent: 22 April 2004 18:11
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
A while back I inserted injars into my plugin.jelly file for the
aspecj
plugin and its been going great. It gives me the ability
to weave an
aspect into a pre-compiled jar. This feature is available
when using
iajc
so it is not something I made up.
Thing is, each time I upgrade or build from CVS I completely forget
that
I had added it and my builds stop working. Is there any way to get
this
added to the maven-aspectj-plugin/plugin.jelly file permanently? It
would
be part of the weave-internal task.
!-- Private goal used to that when the jar:jar postgoal is called
we
don't
have to call aspectj:init and jar:jar twice --
goal name=aspectj:weave-internal
!-- fork to avoid BCEL library version conflict with maven
--
ant:iajc fork=true debug=${maven.aspectj.debug}
outjar=${maven.aspectj.outjar}
injars=${maven.aspectj.injar.nonweaved}
sourceRootCopyFilter=${maven.aspectj.sourceRootCopyFilters}
emacssym=${maven.aspectj.emacssym}
!-- Look for aspect libraries to weave into --
ant:injars
j:forEach var=artifact items=${pom.artifacts}
j:set var=dep value=${artifact.dependency}/
j:if
test=${dep.getProperty('aspect.injar')=='true'}
ant:pathelement location=${artifact.path}/
/j:if
/j:forEach
/ant:injars
/ant:iajc
/goal
It would require jars that are being weaved into to have a
property
defined in the project.xml. I have called this property
aspect.injar.
So:
dependency
groupIdmyjar/groupId
typejar/type
artifactIdmyjar/artifactId
version2.0/version
properties
aspect.injartrue/aspect.injar
/properties
/dependency
How 'bout it? Should I file this in JIRA? Is the mailing
list good
enough?
Also, you can get rid of
copyInjars=true
from the ant:iajc task since it is no longer required by
aspectj-1.1.1.
Let me know your thoughts, I would really like to see this
get added.
Thanks a lot.
Charlie
Vincent Massol wrote:
Yes, that's required. I guess we should add a check in the
plugin to
verify it's defined. Maybe you could file a JIRA issue on
the aspectj
plugin for this.
Thanks
-Vincent
-Original Message-
From: Daniel Henrique Alves Lima
[mailto:[EMAIL PROTECTED]
Sent: 22 April 2004 00:11
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
I've added the following line in my project.xml and the
error seems
to
stop :
aspectSourceDirectorysrc/java/aspectSourceDirectory
Daniel Henrique Alves Lima wrote:
Now i'm getting this already defined message for all my
classes...
Can be a configuration problem ? I don't have any
aspectj plugin
property defined in my project.properties and i'm trying to run
maven aspectj:compile or just maven aspectj.
[iajc] couldn't find aspectjrt.jar on classpath, checked:
[iajc] /projects/new_project/database/RowIterator.jav
a:14 The type RowIterator is already defined
[iajc] public interface RowIterator extends Iterator {
[iajc]
Re: aspectj plugin maven 1.0 rc2
I should be able to get to this next week. I'm flexible with the
aspectj.weave and aspectj.weaveWith. But I'm not exactly clear on what
each one does.
ProjectA: creates projectA.jar - only .class files.
ProjectB: creates projectB.jar - aspects and .class files.
ProjectC: creates projectC.war - uses projectA.jar and projectB.jar
So, in ProjectC's project.xml we would have:
--
dependencies
dependency
groupIdaspect-test/groupId
typejar/type
artifactIdprojectA/artifactId
version1.0/version
properties
war.bundletrue/war.bundle
aspectj.weavetrue/aspectj.weave
/properties
/dependency
dependency
groupIdaspect-test/groupId
typejar/type
artifactIdprojectB/artifactId
version1.0/version
properties
war.bundletrue/war.bundle
aspectj.weaveWithtrue/aspectj.weaveWith
/properties
/dependency
dependency
groupIdaspectj/groupId
typejar/type
artifactIdaspectjtools/artifactId
version1.1.1/version
properties
classloaderroot/classloader
/properties
/dependency
dependency
groupIdaspectj/groupId
typejar/type
artifactIdaspectjrt/artifactId
version1.1.1/version
properties
classloaderroot/classloader
war.bundletrue/war.bundle
/properties
/dependency
/dependencies
--
aspectj.weave: This would use the aspects in ProjectC and weave them into
projectB.jar?
aspectj.weaveWith: This will look in projectB.jar for aspects to use for
weaving in ProjectC classes?
Just wanted to be absolutely clear. I hope this is making sense. Let me
know if I am on the mark or if I am off on these things. Thanks a lot.
Charlie
Carlos Sanchez wrote:
Charles,
Can you apply the patch I've made (
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPASPECTJ-8 ) and then
change aspectj:weave-internal and the xdocs to reflect your changes and
submit it again to Jira?
I think the only thing we should think about are the name of the dependency
properties. I had though about aspectj.weave and aspectj.weaveWith but,
what do you think?
-Mensaje original-
De: Vincent Massol [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 22 de abril de 2004 18:22
Para: 'Maven Users List'
CC: [EMAIL PROTECTED]
Asunto: RE: aspectj plugin maven 1.0 rc2
Hi Charles / Carlos,
Carlos has sent a big patch a few days back. I'm still
fighting to find some time to read it, analyze it and decide
whether we should apply it as is or with some tweaks (I think
we agree to remove the autoweave feature for example). There
are several parameters that come into account, one of them
being the fact that the new version of AspectJ supports
weaving aspects into directories (and not only jars).
Anyway, I have to admit I am a bit overwhelmed and would
appreciate help on this. If Carlos and you could talk this
over and jointly submit a patch that satisfies everyone
(possibly using the latest version of AspectJ), it would help
tremendously. The patch should also include updates to xdocs
and the changes.xml file.
Many thanks
-Vincent
-Original Message-
From: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Sent: 22 April 2004 18:11
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
A while back I inserted injars into my plugin.jelly file for the
aspecj
plugin and its been going great. It gives me the ability
to weave an
aspect into a pre-compiled jar. This feature is available
when using
iajc
so it is not something I made up.
Thing is, each time I upgrade or build from CVS I completely forget
that
I had added it and my builds stop working. Is there any way to get
this
added to the maven-aspectj-plugin/plugin.jelly file permanently? It
would
be part of the weave-internal task.
!-- Private goal used to that when the jar:jar postgoal is called
we
don't
have to call aspectj:init and jar:jar twice --
goal name=aspectj:weave-internal
!-- fork to avoid BCEL library version conflict with maven
--
ant:iajc fork=true debug=${maven.aspectj.debug}
outjar=${maven.aspectj.outjar}
injars=${maven.aspectj.injar.nonweaved}
sourceRootCopyFilter=${maven.aspectj.sourceRootCopyFilters}
emacssym=${maven.aspectj.emacssym}
!-- Look for aspect libraries to weave into --
ant:injars
j:forEach var=artifact items=${pom.artifacts}
j:set var=dep
