There is an open issue in NMaven to investigate the problem of conflicting
packaging names : http://jira.codehaus.org/browse/NMAVEN-65. The most likely
solution is to change the packaging name to include a dotnet: identifier; so
instead of "library", we would use "dotnet:library".
Shane
On 6/13
I am creating a standalone plugin (@requiresProject false,
@requiresDirectInvocation true) that invokes the
org.apache.maven.artifact.resolver.ArtifactResolver.resolveTransitivelymethod.
I also have a
components.xml file within the jar that contains an entry for the artifact
handlers.
or
Brett
>
> On 6/24/05, Shane Isbell <[EMAIL PROTECTED]> wrote:
> > In Maven 1.0, there is a maven.compile.bootclasspath property. Is this
> > property used within Maven 2.0 alpha-2? If not, how do I set the
&g
In Maven 1.0, there is a maven.compile.bootclasspath property. Is this
property used within Maven 2.0 alpha-2? If not, how do I set the
bootclasspath?
Thanks,
Shane
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comma
What is the URL of the Maven 2.0 alpha-3 SVN release?
Thanks,
Shane
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
m SVN
> today, or wait for the release next week. Some of the repository support may
> still need some work, so we'd be interested to hear your experiences.
>
> >
>
> >Cheers,
>
> >Brett
>
> >
>
> >On 6/17/05, Shane Isbel
By separate executions, I mean separate executions of xml.pom[myproject].
On 6/16/05, Shane Isbell <[EMAIL PROTECTED]> wrote:
> Say the project structure is something like
>
>
> ---pom.xml
> +--
> ---pom.xml
> +--
> ---pom.xml
>
> In this case,
elaborate on that? This is the part that is not
> currently supported, the profile executions must be separate.
>
> Thanks,
> Brett
>
> On 6/17/05, Shane Isbell <[EMAIL PROTECTED]> wrote:
> > Hi Brett,
> >
> > The use case is as follows: Each sub project h
> Thus the library would have a unique name, but the dependency on it would say
> if
> I need the jdk 1.4 or jdk 1.5 version.
>
> This may in fact be related to an earlier post by Shane Isbell [EMAIL
> PROTECTED]
> of totally different targets:
> Re: Problem targeting two
27;d like to
> walk through the use case with you.
>
> Cheers,
> Brett
>
> On 6/17/05, Shane Isbell <[EMAIL PROTECTED]> wrote:
> > For my current project, I am testing a migration from ANT to Maven 2.0
> > (alpha 2). I have encountered an issue that I am unable
For my current project, I am testing a migration from ANT to Maven 2.0
(alpha 2). I have encountered an issue that I am unable to resolve. I
have a single source tree, but I need to compile and package a JAR
for two different platforms: J2SE and CDC. I have built two separate
pom.xml files: pom-J2
11 matches
Mail list logo
