Right.
We'll fix it quickly and we'll deploy a new SNAPSHOT.
Is there a bug open in the POM plugin ?

Arnaud

On 8/2/06, Dion Gillard <[EMAIL PROTECTED]> wrote:

Sounds like a bug in the pom plugin.

On 8/3/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Well, it's supposed to be deprecated, see MAVEN-1410. But if I use
> Maven-1.1-beta-3 and do
>
>    maven pom:validate
>
> on a project.xml file that does not have an id, the validation will
> fail. Add an id to project.xml and it validates.
>
> --
> Dennis Lundberg
>
> Arnaud HERITIER wrote:
> > If my memory is good...
> >
> > If Id is a simple name, id is used as a shotcut if groupId=artifactId
thus
> > groupId=id and artifactId=id
> > If id is a compound name id=foo:bar, maven must understand that
groupId=foo
> > and artifact=bar.
> >
> > Id should be deprecated and is just here to maintain the backward
> > compatibility.
> >
> > Open the issue, we'll take a look at it (it will be resolved for the
RC1 if
> > we can't do it for the beta 3).
> >
> > Arnaud
> >
> > On 7/31/06, Daniel Beland <[EMAIL PROTECTED]> wrote:
> >>
> >> I am using the build of 2006-07-23. Whenever I do jar:install or
> >> jar:deploy
> >> or war:install or war:deploy it does it.
> >> Same thing for struts-module plugin or other custom plugins I
developed.
> >>
> >> It seems to come directly from the maven code as it is common to all
> >> plugins
> >> I've tried.
> >>
> >> If I have the following code in the POM:
> >>
> >>   <id>id</id>
> >>   <groupId>group</groupId>
> >>   <artifactId>artifact</artifactId>
> >>   <currentVersion>2.11-beta2</currentVersion>
> >>
> >>
> >> Here is the trace:
> >>
> >>
> >> __  __
> >> |  \/  |__ _Apache__ ___
> >> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> >> |_|  |_\__,_|\_/\___|_||_|  v. 1.1-beta-3-SNAPSHOT
> >>
> >> build:start:
> >>
> >> java:prepare-filesystem:
> >>
> >> java:compile:
> >> xdoclet:hibernatedoclet:
> >>
> >> fix-foreign-keys:
> >>
> >>     [echo] Compiling to
c:\eclipse\workspace\DBInterface/target/classes
> >>     [echo]
> >> ==========================================================
> >>
> >>   WARNING:  maven.compile.target is not set:
> >>             using the default value which depends on your JVM
> >>
> >> ==========================================================
> >>
> >>
> >> java:jar-resources:
> >> copy-hbm-files:
> >>
> >>
> >> test:test:
> >>
> >> jar:jar:
> >>
> >> jar:install:
> >>     [echo] Installing...
> >> Uploading to group/jars/id-2.11-beta2.jar:
> >> .................... (467K)
> >> Uploading to group/poms/id-2.11-beta2.pom:
> >> .................... (16K)
> >> BUILD SUCCESSFUL
> >> Total time   : 12 seconds
> >> Finished at  : Monday, July 31, 2006 10:02:49 BST AM
> >>
> >> I'll open a bug in jira
> >>
> >> On 7/29/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> >> >
> >> > Where did you read that in maven 1.1 <id> is used instead of
> >> > <artifactId>? It should be just the other way round, we have
replaced
> >> > <id> by the combination <groupId><artifactId>. However, there are
> >> > probably still some inconsistencies (see eg [1]), so it would be
> >> good to
> >> > know where you ran into problems with this?
> >> >
> >> > Cheers,
> >> > -Lukas
> >> >
> >> > [1] http://jira.codehaus.org/browse/MAVEN-1704
> >> >
> >> >
> >> > Daniel Beland wrote:
> >> > > Hi,
> >> > >
> >> > >
> >> > > in maven 1.0.2, when I install or deploy an artifact, it is put
in
> >> the
> >> > > <groupId> directory under <type>s and the artifact is named
> >> > > <artifactId>.<type>
> >> > >
> >> > > Now in maven 1.1, the artifact is named <id> instead of
<artifactId>.
> >> I
> >> > was
> >> > > not using this tag previously I think Mevenide defaults it to
> >> > > <groupId>:<artifactId> so obviously it causes problems because it
is
> >> not
> >> > > named as before and it is not deployed at all (I think the colon
is
> >> not
> >> > > supported in the file name).
> >> > >
> >> > >
> >> > > On the web site it says this:
> >> > > id  The short name of the project. This value is used when naming
> >> > > jars<http://maven.apache.org/maven-1.x/plugins/java/index.html
>and
> >> > > distribution
> >> > > files <http://maven.apache.org/maven-1.x/plugins/dist/index.html
>.
> >> > > groupId The short name of the project group. This value is used
to
> >> > > group all jars
> >> > > for a project in one directory. For more info look at the user
> >> > > guide<
http://maven.apache.org/maven-1.x/reference/conventions.html>.
> >> > >  artifactId  The short name of the project. This value is used in
> >> > > conjunction with groupId when naming
> >> > > jars<http://maven.apache.org/maven-1.x/plugins/java/index.html
>and
> >> > > distribution
> >> > > files <http://maven.apache.org/maven-1.x/plugins/dist/index.html
>.
> >> > >
> >> > > I don't mind updating all my project files, I just want to make
sure
> >> it
> >> > is
> >> > > the expected behaviour from now on before I do it?
> >> > >
> >> > >
> >> > > Thanks,
> >> > > Daniel
> >> > >
> >> >
> >> >
---------------------------------------------------------------------
> >> > 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]
>
>


--
http://www.multitask.com.au/people/dion/
"If you even dream of beating me you'd better wake up and apologize" -
Muhammad Ali

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to