I think I have found an issue in WTP integration.
When I modify a resource that is in the default resource folder
(src/main/resource), it is published to Tomcat, no problem.
When I modify a resource that is in another resource folder (config), it is
published to Tomcat when I create the server, but modification I do after
that are not taken in account, even with a clean/rebuild and stop/start.
Please find bellow some part of my pom.xml and profiles.xml. In my Maven
project configuration, profile env-local is activated.
pom.xml
<resources>
<resource>
<directory>src/main/resources</directory>
</resource>
<resource>
<directory>src/test/resources</directory>
</resource>
<resource>
<directory>${config-dir}</directory>
</resource>
</resources>
profiles.xml
<profile>
<id>env-local</id>
<activation>
<property>
<name>env</name>
<value>local</value>
</property>
</activation>
<properties>
<config.dir>config</config.dir>
</properties>
</profile>
On Thu, May 15, 2008 at 9:28 AM, sebdotv <[EMAIL PROTECTED]> wrote:
> Sure, done: http://jira.codehaus.org/browse/MNGECLIPSE-601
>
> On Wed, May 14, 2008 at 7:24 PM, Igor Fedorenko <[EMAIL PROTECTED]>
> wrote:
> > Can you please open an enhancement request for m2e to do this?
> >
> > sebdotv wrote:
> >>
> >> Before m2eclipse introduced this feature, I used to manually add the
> >> output folders of those projects to the aspect path.
> >>
> >> On Wed, May 14, 2008 at 4:16 PM, Igor Fedorenko <[EMAIL PROTECTED]>
> >> wrote:
> >>>
> >>> Sebastien,
> >>>
> >>> This seems to be AJDT limitation -- it does not allow workspace project
> >>> references in inpath/aspectpath. Do you know how to set it up manually?
> >>>
> >>> I tried to get clarification on AJDT developers but no reply yet as of
> >>> yet.
> >>> Maybe I should try dev mailing list instead of the newsgroup...
> >>>
> >>> sebdotv wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I tried 0.9.4 dev and I must say I'm very impressed by the AJDT
> >>>> integration. Good job!
> >>>>
> >>>> Aspect Path is correctly configured as jar files for projects not
> >>>> present in the workspace, but if projects are present in the workspace
> >>>> (and workspace resolution is active), then M2Eclipse seems to skip
> >>>> those projects from the aspect path. I'll try to create a minimal set
> >>>> of test projects to show this issue.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Sebastien
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe from this list, please visit:
> >>>>
> >>>> http://xircles.codehaus.org/manage_email
> >>>>
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe from this list, please visit:
> >>>
> >>> http://xircles.codehaus.org/manage_email
> >>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list, please visit:
> >>
> >> http://xircles.codehaus.org/manage_email
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
