You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Eric Chow <ec...@macaucabletv.com> on 2004/07/23 04:08:05 UTC
Maven Tomcat Plugin problem when precompile JSP !!
Hello,
I need to precompile the JSP before deployment.
In my JSPs, they require some taglib(TLDs). I set them as dependence in the
project.xml.
But when I call tomcat:jspc, it just raised exception that "can't locate
those TLDs ...".
Finally, I have to copy those TLDs into the /WEB-INF/tlds for compile them.
Anyway, why Tomcat plugin can't check those TLDs dependences ????
Eric
==========================
If you know what you are doing,
it is not called RESEARCH!
==========================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: using different project.xml
Posted by Heiko Kundlacz <he...@qnamic.com>.
Sorry for my Mail. It works fine.
Hopefully nobody has wasted time, because of my stupid posting :o)
Heiko
Heiko Kundlacz wrote:
> Hi all
>
> I have seen a parameter maven --pom and want to use different
> project.xml (project_product1.xml and so on).
>
> Maven --help says: -p,--pom arg Set project file
>
> But it won't be used. Does anybody of you have some experience with
> such a problem?
>
> Heiko
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
--
------------------------------------------------------
Heiko Kundlacz | MailTo: heiko.kundlacz@qnamic.com
Qnamic AG | Tel: +41 62 209 7056
Fabrikstr. 10 | Natel: +41 78 861 4006
4614 Haegendorf | Fax: +41 62 209 7044
Switzerland | Homepage: http://www.qnamic.com
------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
using different project.xml
Posted by Heiko Kundlacz <he...@qnamic.com>.
Hi all
I have seen a parameter maven --pom and want to use different
project.xml (project_product1.xml and so on).
Maven --help says: -p,--pom arg Set project file
But it won't be used. Does anybody of you have some experience with such
a problem?
Heiko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: optional aspects
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
Hi,
I've taken a look and see that no documentation nor tests are attached, if
you make it it will be faster, else I'll have to do myself and will delay a
bit applying the patch.
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -----Original Message-----
> From: Mark Proctor [mailto:lists@markproctor.com]
> Sent: Monday, August 02, 2004 10:28 PM
> To: Maven Users List
> Cc: apache@carlos.cousas.net
> Subject: Re: optional aspects
>
> done - http://jira.codehaus.org/browse/MPASPECTJ-12
> Can you please review and let me know when this is likely to
> be included, if its ok.
>
> Thanks
>
> Mark
> Carlos Sanchez wrote:
>
> >Hi Mark,
> >
> >Could you please create a patch and submit to JIRA do it will be
> >included in next plugin version?
> >http://jira.codehaus.org/browse/MPASPECTJ
> >
> >If you need help, don't hesitate on asking me.
> >
> >Regards
> >
> >Carlos Sanchez
> >A Coruña, Spain
> >
> >Oness Project
> >http://oness.sourceforge.net
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: Mark Proctor [mailto:lists@markproctor.com]
> >>Sent: Friday, July 30, 2004 7:18 PM
> >>To: Maven Users List; apache@carlos.cousas.net
> >>Subject: Re: optional aspects
> >>
> >>Carlos,
> >>
> >>I can put the aspects to compile .aspect files and
> reference it like
> >>below
> >> <ant:argfiles>
> >> <pathelement location="trace.aspect"/>
> >> <pathelement location="event-model.aspect"/>
> >> </ant:argfiles>
> >>and then updated sourceRoots, as you can't have both - one or the
> >>other:
> >> <ant:sourceroots>
> >> <ant:path refid="${sourcePathRefid}"/>
> >> <!--
> >> <j:if test="${aspectSourcesPresent == 'true'}">
> >> <ant:pathelement
> >>location="${pom.build.aspectSourceDirectory}"/>
> >> </j:if>
> >> -->
> >> </ant:sourceroots>
> >>Downside is you have to create files to specify the aspects, but
> >>atleast its doable. So I can create a .aspect file for each
> aspect I
> >>want to weave. I still need some way to specify those
> locations as a
> >>maven property.
> >>I then need to say if aspects file property is specified then use
> >>that, else specify ${pom.build.aspectSourceDirectory} in
> >>ant:sourceroots as normal.
> >>
> >>Mark
> >>Carlos Sanchez wrote:
> >>
> >>
> >>
> >>>Feel free to CCing your findings to me.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Mark Proctor [mailto:lists@markproctor.com]
> >>>>Sent: Friday, July 30, 2004 5:54 PM
> >>>>To: Maven Users List
> >>>>Subject: Re: optional aspects
> >>>>
> >>>>Just tried testing the plugin with the code change below,
> but that
> >>>>failed, will look into that list option now:
> >>>>
> >>>> <ant:sourceroots>
> >>>> <ant:path refid="${sourcePathRefid}"/>
> >>>> <ant:path>
> >>>> <fileset dir="${pom.build.aspectSourceDirectory}">
> >>>> <includes>
> >>>> <include name="**/*EventModel.java"/>
> >>>> <include name="**/*Trace.java"/>
> >>>> <include name="**/*EntryMethod.java"/>
> >>>> </includes>
> >>>> </fileset>
> >>>> </ant:path>
> >>>> <!--
> >>>> <j:if test="${aspectSourcesPresent == 'true'}">
> >>>> <ant:pathelement
> >>>>location="${pom.build.aspectSourceDirectory}"/>
> >>>> </j:if>
> >>>> -->
> >>>> </ant:sourceroots>
> >>>>------------
> >>>>MessageHolder: (3 error) (1 fail) (1 abort)
> >>>>[error 0]: error build config error: bad sourceroot:
> >>>>D:\java\eclipse\workspace
> >>>>s\drools\drools-core\src\aspects\org\drools\MethodEntry.java
> >>>>[error 1]: error build config error: bad sourceroot:
> >>>>D:\java\eclipse\workspace
> >>>>s\drools\drools-core\src\aspects\org\drools\reteoo\DroolsEvent
> >>>>Model.java
> >>>>[error 2]: error build config error: bad sourceroot:
> >>>>D:\java\eclipse\workspace
> >>>>s\drools\drools-core\src\aspects\org\drools\Trace.java
> >>>>
> >>>>Carlos Sanchez wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>Hi,
> >>>>>
> >>>>>I suggest you to check this thread on aspectj-users mailing list
> >>>>>http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg02478.html
> >>>>>titled "POLL: How do you use ".lst" files with AJDT in Eclipse?"
> >>>>>and https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454
> >>>>>
> >>>>>The aspectj maven plugin uses iajc ant task, so if you can
> >>>>>
> >>>>>
> >>point out
> >>
> >>
> >>>>>something about adding conditional weaving I'll be happy to
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>add it to
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>the plugin.
> >>>>>
> >>>>>Regards
> >>>>>
> >>>>>Carlos Sanchez
> >>>>>A Coruña, Spain
> >>>>>
> >>>>>Oness Project
> >>>>>http://oness.sourceforge.net
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>-----Original Message-----
> >>>>>>From: Mark Proctor [mailto:lists@markproctor.com]
> >>>>>>Sent: Friday, July 30, 2004 4:29 PM
> >>>>>>To: Maven Users List
> >>>>>>Subject: optional aspects
> >>>>>>
> >>>>>>We are building up a suite of aspects with aspectj to help with
> >>>>>>testing/debugging. We want to be able to choose which
> aspects are
> >>>>>>weaved at compile time with property settings, is this possible?
> >>>>>>
> >>>>>>I was hoping I could do:
> >>>>>>maven.aspectj.sourceRootCopyFilter=**/drools/Trace.java,
> >>>>>>**/drools/Trace/MethodEntry.java
> >>>>>>
> >>>>>>But that is obviously just for resource copying, ideally I
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>need to be
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>>able to exclude/include aspects.
> >>>>>>
> >>>>>>Mark
> >>>>>>
> >>>>>>
> >>>>>>------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>---------
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>>>>>For additional commands, e-mail: users-help@maven.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>-----------------------------------------------------------
> >>>>>
> >>>>>
> >>----------
> >>
> >>
> >>>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>>>>For additional commands, e-mail: users-help@maven.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>-----------------------------------------------------------
> ----------
> >>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>>For additional commands, e-mail: users-help@maven.apache.org
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: optional aspects
Posted by Mark Proctor <li...@markproctor.com>.
done - http://jira.codehaus.org/browse/MPASPECTJ-12
Can you please review and let me know when this is likely to be
included, if its ok.
Thanks
Mark
Carlos Sanchez wrote:
>Hi Mark,
>
>Could you please create a patch and submit to JIRA do it will be included in
>next plugin version?
>http://jira.codehaus.org/browse/MPASPECTJ
>
>If you need help, don't hesitate on asking me.
>
>Regards
>
>Carlos Sanchez
>A Coruña, Spain
>
>Oness Project
>http://oness.sourceforge.net
>
>
>
>
>>-----Original Message-----
>>From: Mark Proctor [mailto:lists@markproctor.com]
>>Sent: Friday, July 30, 2004 7:18 PM
>>To: Maven Users List; apache@carlos.cousas.net
>>Subject: Re: optional aspects
>>
>>Carlos,
>>
>>I can put the aspects to compile .aspect files and reference
>>it like below
>> <ant:argfiles>
>> <pathelement location="trace.aspect"/>
>> <pathelement location="event-model.aspect"/>
>> </ant:argfiles>
>>and then updated sourceRoots, as you can't have both - one or
>>the other:
>> <ant:sourceroots>
>> <ant:path refid="${sourcePathRefid}"/>
>> <!--
>> <j:if test="${aspectSourcesPresent == 'true'}">
>> <ant:pathelement
>>location="${pom.build.aspectSourceDirectory}"/>
>> </j:if>
>> -->
>> </ant:sourceroots>
>>Downside is you have to create files to specify the aspects,
>>but atleast its doable. So I can create a .aspect file for
>>each aspect I want to weave. I still need some way to specify
>>those locations as a maven property.
>>I then need to say if aspects file property is specified then
>>use that, else specify ${pom.build.aspectSourceDirectory} in
>>ant:sourceroots as normal.
>>
>>Mark
>>Carlos Sanchez wrote:
>>
>>
>>
>>>Feel free to CCing your findings to me.
>>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Mark Proctor [mailto:lists@markproctor.com]
>>>>Sent: Friday, July 30, 2004 5:54 PM
>>>>To: Maven Users List
>>>>Subject: Re: optional aspects
>>>>
>>>>Just tried testing the plugin with the code change below, but that
>>>>failed, will look into that list option now:
>>>>
>>>> <ant:sourceroots>
>>>> <ant:path refid="${sourcePathRefid}"/>
>>>> <ant:path>
>>>> <fileset dir="${pom.build.aspectSourceDirectory}">
>>>> <includes>
>>>> <include name="**/*EventModel.java"/>
>>>> <include name="**/*Trace.java"/>
>>>> <include name="**/*EntryMethod.java"/>
>>>> </includes>
>>>> </fileset>
>>>> </ant:path>
>>>> <!--
>>>> <j:if test="${aspectSourcesPresent == 'true'}">
>>>> <ant:pathelement
>>>>location="${pom.build.aspectSourceDirectory}"/>
>>>> </j:if>
>>>> -->
>>>> </ant:sourceroots>
>>>>------------
>>>>MessageHolder: (3 error) (1 fail) (1 abort)
>>>>[error 0]: error build config error: bad sourceroot:
>>>>D:\java\eclipse\workspace
>>>>s\drools\drools-core\src\aspects\org\drools\MethodEntry.java
>>>>[error 1]: error build config error: bad sourceroot:
>>>>D:\java\eclipse\workspace
>>>>s\drools\drools-core\src\aspects\org\drools\reteoo\DroolsEvent
>>>>Model.java
>>>>[error 2]: error build config error: bad sourceroot:
>>>>D:\java\eclipse\workspace
>>>>s\drools\drools-core\src\aspects\org\drools\Trace.java
>>>>
>>>>Carlos Sanchez wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>I suggest you to check this thread on aspectj-users mailing list
>>>>>http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg02478.html
>>>>>titled "POLL: How do you use ".lst" files with AJDT in Eclipse?"
>>>>>and https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454
>>>>>
>>>>>The aspectj maven plugin uses iajc ant task, so if you can
>>>>>
>>>>>
>>point out
>>
>>
>>>>>something about adding conditional weaving I'll be happy to
>>>>>
>>>>>
>>>>>
>>>>>
>>>>add it to
>>>>
>>>>
>>>>
>>>>
>>>>>the plugin.
>>>>>
>>>>>Regards
>>>>>
>>>>>Carlos Sanchez
>>>>>A Coruña, Spain
>>>>>
>>>>>Oness Project
>>>>>http://oness.sourceforge.net
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: Mark Proctor [mailto:lists@markproctor.com]
>>>>>>Sent: Friday, July 30, 2004 4:29 PM
>>>>>>To: Maven Users List
>>>>>>Subject: optional aspects
>>>>>>
>>>>>>We are building up a suite of aspects with aspectj to help with
>>>>>>testing/debugging. We want to be able to choose which aspects are
>>>>>>weaved at compile time with property settings, is this possible?
>>>>>>
>>>>>>I was hoping I could do:
>>>>>>maven.aspectj.sourceRootCopyFilter=**/drools/Trace.java,
>>>>>>**/drools/Trace/MethodEntry.java
>>>>>>
>>>>>>But that is obviously just for resource copying, ideally I
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>need to be
>>>>
>>>>
>>>>
>>>>
>>>>>>able to exclude/include aspects.
>>>>>>
>>>>>>Mark
>>>>>>
>>>>>>
>>>>>>------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>---------
>>>>
>>>>
>>>>
>>>>
>>>>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>>For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>-----------------------------------------------------------
>>>>>
>>>>>
>>----------
>>
>>
>>>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
RE: optional aspects
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
Hi Mark,
Could you please create a patch and submit to JIRA do it will be included in
next plugin version?
http://jira.codehaus.org/browse/MPASPECTJ
If you need help, don't hesitate on asking me.
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -----Original Message-----
> From: Mark Proctor [mailto:lists@markproctor.com]
> Sent: Friday, July 30, 2004 7:18 PM
> To: Maven Users List; apache@carlos.cousas.net
> Subject: Re: optional aspects
>
> Carlos,
>
> I can put the aspects to compile .aspect files and reference
> it like below
> <ant:argfiles>
> <pathelement location="trace.aspect"/>
> <pathelement location="event-model.aspect"/>
> </ant:argfiles>
> and then updated sourceRoots, as you can't have both - one or
> the other:
> <ant:sourceroots>
> <ant:path refid="${sourcePathRefid}"/>
> <!--
> <j:if test="${aspectSourcesPresent == 'true'}">
> <ant:pathelement
> location="${pom.build.aspectSourceDirectory}"/>
> </j:if>
> -->
> </ant:sourceroots>
> Downside is you have to create files to specify the aspects,
> but atleast its doable. So I can create a .aspect file for
> each aspect I want to weave. I still need some way to specify
> those locations as a maven property.
> I then need to say if aspects file property is specified then
> use that, else specify ${pom.build.aspectSourceDirectory} in
> ant:sourceroots as normal.
>
> Mark
> Carlos Sanchez wrote:
>
> >Feel free to CCing your findings to me.
> >
> >
> >
> >>-----Original Message-----
> >>From: Mark Proctor [mailto:lists@markproctor.com]
> >>Sent: Friday, July 30, 2004 5:54 PM
> >>To: Maven Users List
> >>Subject: Re: optional aspects
> >>
> >>Just tried testing the plugin with the code change below, but that
> >>failed, will look into that list option now:
> >>
> >> <ant:sourceroots>
> >> <ant:path refid="${sourcePathRefid}"/>
> >> <ant:path>
> >> <fileset dir="${pom.build.aspectSourceDirectory}">
> >> <includes>
> >> <include name="**/*EventModel.java"/>
> >> <include name="**/*Trace.java"/>
> >> <include name="**/*EntryMethod.java"/>
> >> </includes>
> >> </fileset>
> >> </ant:path>
> >> <!--
> >> <j:if test="${aspectSourcesPresent == 'true'}">
> >> <ant:pathelement
> >>location="${pom.build.aspectSourceDirectory}"/>
> >> </j:if>
> >> -->
> >> </ant:sourceroots>
> >>------------
> >>MessageHolder: (3 error) (1 fail) (1 abort)
> >>[error 0]: error build config error: bad sourceroot:
> >>D:\java\eclipse\workspace
> >>s\drools\drools-core\src\aspects\org\drools\MethodEntry.java
> >>[error 1]: error build config error: bad sourceroot:
> >>D:\java\eclipse\workspace
> >>s\drools\drools-core\src\aspects\org\drools\reteoo\DroolsEvent
> >>Model.java
> >>[error 2]: error build config error: bad sourceroot:
> >>D:\java\eclipse\workspace
> >>s\drools\drools-core\src\aspects\org\drools\Trace.java
> >>
> >>Carlos Sanchez wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>I suggest you to check this thread on aspectj-users mailing list
> >>>http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg02478.html
> >>>titled "POLL: How do you use ".lst" files with AJDT in Eclipse?"
> >>>and https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454
> >>>
> >>>The aspectj maven plugin uses iajc ant task, so if you can
> point out
> >>>something about adding conditional weaving I'll be happy to
> >>>
> >>>
> >>add it to
> >>
> >>
> >>>the plugin.
> >>>
> >>>Regards
> >>>
> >>>Carlos Sanchez
> >>>A Coruña, Spain
> >>>
> >>>Oness Project
> >>>http://oness.sourceforge.net
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Mark Proctor [mailto:lists@markproctor.com]
> >>>>Sent: Friday, July 30, 2004 4:29 PM
> >>>>To: Maven Users List
> >>>>Subject: optional aspects
> >>>>
> >>>>We are building up a suite of aspects with aspectj to help with
> >>>>testing/debugging. We want to be able to choose which aspects are
> >>>>weaved at compile time with property settings, is this possible?
> >>>>
> >>>>I was hoping I could do:
> >>>>maven.aspectj.sourceRootCopyFilter=**/drools/Trace.java,
> >>>>**/drools/Trace/MethodEntry.java
> >>>>
> >>>>But that is obviously just for resource copying, ideally I
> >>>>
> >>>>
> >>need to be
> >>
> >>
> >>>>able to exclude/include aspects.
> >>>>
> >>>>Mark
> >>>>
> >>>>
> >>>>------------------------------------------------------------
> >>>>
> >>>>
> >>---------
> >>
> >>
> >>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>>>For additional commands, e-mail: users-help@maven.apache.org
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>-----------------------------------------------------------
> ----------
> >>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>>For additional commands, e-mail: users-help@maven.apache.org
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: optional aspects
Posted by Mark Proctor <li...@markproctor.com>.
Carlos,
I can put the aspects to compile .aspect files and reference it like below
<ant:argfiles>
<pathelement location="trace.aspect"/>
<pathelement location="event-model.aspect"/>
</ant:argfiles>
and then updated sourceRoots, as you can't have both - one or the other:
<ant:sourceroots>
<ant:path refid="${sourcePathRefid}"/>
<!--
<j:if test="${aspectSourcesPresent == 'true'}">
<ant:pathelement location="${pom.build.aspectSourceDirectory}"/>
</j:if>
-->
</ant:sourceroots>
Downside is you have to create files to specify the aspects, but atleast
its doable. So I can create a .aspect file for each aspect I want to
weave. I still need some way to specify those locations as a maven property.
I then need to say if aspects file property is specified then use that,
else specify ${pom.build.aspectSourceDirectory} in ant:sourceroots as
normal.
Mark
Carlos Sanchez wrote:
>Feel free to CCing your findings to me.
>
>
>
>>-----Original Message-----
>>From: Mark Proctor [mailto:lists@markproctor.com]
>>Sent: Friday, July 30, 2004 5:54 PM
>>To: Maven Users List
>>Subject: Re: optional aspects
>>
>>Just tried testing the plugin with the code change below, but
>>that failed, will look into that list option now:
>>
>> <ant:sourceroots>
>> <ant:path refid="${sourcePathRefid}"/>
>> <ant:path>
>> <fileset dir="${pom.build.aspectSourceDirectory}">
>> <includes>
>> <include name="**/*EventModel.java"/>
>> <include name="**/*Trace.java"/>
>> <include name="**/*EntryMethod.java"/>
>> </includes>
>> </fileset>
>> </ant:path>
>> <!--
>> <j:if test="${aspectSourcesPresent == 'true'}">
>> <ant:pathelement
>>location="${pom.build.aspectSourceDirectory}"/>
>> </j:if>
>> -->
>> </ant:sourceroots>
>>------------
>>MessageHolder: (3 error) (1 fail) (1 abort)
>>[error 0]: error build config error: bad sourceroot:
>>D:\java\eclipse\workspace
>>s\drools\drools-core\src\aspects\org\drools\MethodEntry.java
>>[error 1]: error build config error: bad sourceroot:
>>D:\java\eclipse\workspace
>>s\drools\drools-core\src\aspects\org\drools\reteoo\DroolsEvent
>>Model.java
>>[error 2]: error build config error: bad sourceroot:
>>D:\java\eclipse\workspace
>>s\drools\drools-core\src\aspects\org\drools\Trace.java
>>
>>Carlos Sanchez wrote:
>>
>>
>>
>>>Hi,
>>>
>>>I suggest you to check this thread on aspectj-users mailing list
>>>http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg02478.html
>>>titled "POLL: How do you use ".lst" files with AJDT in Eclipse?"
>>>and https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454
>>>
>>>The aspectj maven plugin uses iajc ant task, so if you can point out
>>>something about adding conditional weaving I'll be happy to
>>>
>>>
>>add it to
>>
>>
>>>the plugin.
>>>
>>>Regards
>>>
>>>Carlos Sanchez
>>>A Coruña, Spain
>>>
>>>Oness Project
>>>http://oness.sourceforge.net
>>>
>>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Mark Proctor [mailto:lists@markproctor.com]
>>>>Sent: Friday, July 30, 2004 4:29 PM
>>>>To: Maven Users List
>>>>Subject: optional aspects
>>>>
>>>>We are building up a suite of aspects with aspectj to help with
>>>>testing/debugging. We want to be able to choose which aspects are
>>>>weaved at compile time with property settings, is this possible?
>>>>
>>>>I was hoping I could do:
>>>>maven.aspectj.sourceRootCopyFilter=**/drools/Trace.java,
>>>>**/drools/Trace/MethodEntry.java
>>>>
>>>>But that is obviously just for resource copying, ideally I
>>>>
>>>>
>>need to be
>>
>>
>>>>able to exclude/include aspects.
>>>>
>>>>Mark
>>>>
>>>>
>>>>------------------------------------------------------------
>>>>
>>>>
>>---------
>>
>>
>>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
RE: optional aspects
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
Feel free to CCing your findings to me.
> -----Original Message-----
> From: Mark Proctor [mailto:lists@markproctor.com]
> Sent: Friday, July 30, 2004 5:54 PM
> To: Maven Users List
> Subject: Re: optional aspects
>
> Just tried testing the plugin with the code change below, but
> that failed, will look into that list option now:
>
> <ant:sourceroots>
> <ant:path refid="${sourcePathRefid}"/>
> <ant:path>
> <fileset dir="${pom.build.aspectSourceDirectory}">
> <includes>
> <include name="**/*EventModel.java"/>
> <include name="**/*Trace.java"/>
> <include name="**/*EntryMethod.java"/>
> </includes>
> </fileset>
> </ant:path>
> <!--
> <j:if test="${aspectSourcesPresent == 'true'}">
> <ant:pathelement
> location="${pom.build.aspectSourceDirectory}"/>
> </j:if>
> -->
> </ant:sourceroots>
> ------------
> MessageHolder: (3 error) (1 fail) (1 abort)
> [error 0]: error build config error: bad sourceroot:
> D:\java\eclipse\workspace
> s\drools\drools-core\src\aspects\org\drools\MethodEntry.java
> [error 1]: error build config error: bad sourceroot:
> D:\java\eclipse\workspace
> s\drools\drools-core\src\aspects\org\drools\reteoo\DroolsEvent
> Model.java
> [error 2]: error build config error: bad sourceroot:
> D:\java\eclipse\workspace
> s\drools\drools-core\src\aspects\org\drools\Trace.java
>
> Carlos Sanchez wrote:
>
> >Hi,
> >
> >I suggest you to check this thread on aspectj-users mailing list
> >http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg02478.html
> >titled "POLL: How do you use ".lst" files with AJDT in Eclipse?"
> >and https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454
> >
> >The aspectj maven plugin uses iajc ant task, so if you can point out
> >something about adding conditional weaving I'll be happy to
> add it to
> >the plugin.
> >
> >Regards
> >
> >Carlos Sanchez
> >A Coruña, Spain
> >
> >Oness Project
> >http://oness.sourceforge.net
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: Mark Proctor [mailto:lists@markproctor.com]
> >>Sent: Friday, July 30, 2004 4:29 PM
> >>To: Maven Users List
> >>Subject: optional aspects
> >>
> >>We are building up a suite of aspects with aspectj to help with
> >>testing/debugging. We want to be able to choose which aspects are
> >>weaved at compile time with property settings, is this possible?
> >>
> >>I was hoping I could do:
> >>maven.aspectj.sourceRootCopyFilter=**/drools/Trace.java,
> >>**/drools/Trace/MethodEntry.java
> >>
> >>But that is obviously just for resource copying, ideally I
> need to be
> >>able to exclude/include aspects.
> >>
> >>Mark
> >>
> >>
> >>------------------------------------------------------------
> ---------
> >>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: optional aspects
Posted by Mark Proctor <li...@markproctor.com>.
Just tried testing the plugin with the code change below, but that
failed, will look into that list option now:
<ant:sourceroots>
<ant:path refid="${sourcePathRefid}"/>
<ant:path>
<fileset dir="${pom.build.aspectSourceDirectory}">
<includes>
<include name="**/*EventModel.java"/>
<include name="**/*Trace.java"/>
<include name="**/*EntryMethod.java"/>
</includes>
</fileset>
</ant:path>
<!--
<j:if test="${aspectSourcesPresent == 'true'}">
<ant:pathelement location="${pom.build.aspectSourceDirectory}"/>
</j:if>
-->
</ant:sourceroots>
------------
MessageHolder: (3 error) (1 fail) (1 abort)
[error 0]: error build config error: bad sourceroot: D:\java\eclipse\workspace
s\drools\drools-core\src\aspects\org\drools\MethodEntry.java
[error 1]: error build config error: bad sourceroot: D:\java\eclipse\workspace
s\drools\drools-core\src\aspects\org\drools\reteoo\DroolsEventModel.java
[error 2]: error build config error: bad sourceroot: D:\java\eclipse\workspace
s\drools\drools-core\src\aspects\org\drools\Trace.java
Carlos Sanchez wrote:
>Hi,
>
>I suggest you to check this thread on aspectj-users mailing list
>http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg02478.html
>titled "POLL: How do you use ".lst" files with AJDT in Eclipse?"
>and https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454
>
>The aspectj maven plugin uses iajc ant task, so if you can point out
>something about adding conditional weaving I'll be happy to add it to the
>plugin.
>
>Regards
>
>Carlos Sanchez
>A Coruña, Spain
>
>Oness Project
>http://oness.sourceforge.net
>
>
>
>
>>-----Original Message-----
>>From: Mark Proctor [mailto:lists@markproctor.com]
>>Sent: Friday, July 30, 2004 4:29 PM
>>To: Maven Users List
>>Subject: optional aspects
>>
>>We are building up a suite of aspects with aspectj to help
>>with testing/debugging. We want to be able to choose which
>>aspects are weaved at compile time with property settings, is
>>this possible?
>>
>>I was hoping I could do:
>>maven.aspectj.sourceRootCopyFilter=**/drools/Trace.java,
>>**/drools/Trace/MethodEntry.java
>>
>>But that is obviously just for resource copying, ideally I
>>need to be able to exclude/include aspects.
>>
>>Mark
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
RE: optional aspects
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
Hi,
I suggest you to check this thread on aspectj-users mailing list
http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg02478.html
titled "POLL: How do you use ".lst" files with AJDT in Eclipse?"
and https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454
The aspectj maven plugin uses iajc ant task, so if you can point out
something about adding conditional weaving I'll be happy to add it to the
plugin.
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -----Original Message-----
> From: Mark Proctor [mailto:lists@markproctor.com]
> Sent: Friday, July 30, 2004 4:29 PM
> To: Maven Users List
> Subject: optional aspects
>
> We are building up a suite of aspects with aspectj to help
> with testing/debugging. We want to be able to choose which
> aspects are weaved at compile time with property settings, is
> this possible?
>
> I was hoping I could do:
> maven.aspectj.sourceRootCopyFilter=**/drools/Trace.java,
> **/drools/Trace/MethodEntry.java
>
> But that is obviously just for resource copying, ideally I
> need to be able to exclude/include aspects.
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
optional aspects
Posted by Mark Proctor <li...@markproctor.com>.
We are building up a suite of aspects with aspectj to help with
testing/debugging. We want to be able to choose which aspects are weaved
at compile time with property settings, is this possible?
I was hoping I could do:
maven.aspectj.sourceRootCopyFilter=**/drools/Trace.java,
**/drools/Trace/MethodEntry.java
But that is obviously just for resource copying, ideally I need to be
able to exclude/include aspects.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven Tomcat Plugin problem when precompile JSP !!
Posted by Nathan Coast <na...@codeczar.com>.
no reason at all :)
feel free to send me a patch
Eric Chow wrote:
> Hello,
>
> I need to precompile the JSP before deployment.
>
> In my JSPs, they require some taglib(TLDs). I set them as dependence in the
> project.xml.
>
> But when I call tomcat:jspc, it just raised exception that "can't locate
> those TLDs ...".
>
> Finally, I have to copy those TLDs into the /WEB-INF/tlds for compile them.
>
>
> Anyway, why Tomcat plugin can't check those TLDs dependences ????
>
>
> Eric
>
> ==========================
> If you know what you are doing,
> it is not called RESEARCH!
> ==========================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: release plugin future
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
Hi,
To make releases you should use the scm:prepare-release and
scm:perform-release goals.
For distributions you can use the distribution plugin, if it suits your
needs.
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -----Original Message-----
> From: Marcin Gurbisz [mailto:Marcin.Gurbisz@pentacomp.com.pl]
> Sent: Monday, August 09, 2004 12:00 PM
> To: Maven Users List
> Subject: release plugin future
>
> I'm thinking about automating releasing tasks and building
> distributions.
> I was about to check how maven release plugin works, but I
> saw that it has just been deprecated.
> What is a future of releasing?
>
> Thanks,
> Marcin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
release plugin future
Posted by Marcin Gurbisz <Ma...@pentacomp.com.pl>.
I'm thinking about automating releasing tasks and building distributions.
I was about to check how maven release plugin works, but I saw that it
has just been deprecated.
What is a future of releasing?
Thanks,
Marcin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org