>>>>> Arnaud Bailly <[EMAIL PROTECTED]>:
> Steinar Bang <[EMAIL PROTECTED]> writes:
>> What does <packaging>pom</packaging> imply? In particular: why would
>> one choose <packaging>pom</packaging> over <packaging>jar</packaging>?
> Packgaging type is the single most important feature of a pom as it
> defines the binding of mojos to the lifecycle used to builde that
> project, which means what is done at what time. Packaging "pom" is
> for toplevel projects without sources, and not much is done with
> this packaging. Packaging jar is the standard one for projects with
> sources to compile, test and deploy.
That's what I thought. But in this case it seemed to be an artifact
with packaging "pom", that produces a jar.
But as it turns out, I was looking at the wrong pom.xml. The project
consists of a _lot_ of them.
Anyway I've now tried
mvn source:jar repository:bundle-create
That gave me the following error message:
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] project.url must be present.
[INFO] ------------------------------------------------------------------------
I've tried the four combinations below, without success:
mvn -Dproject.url="http://localhost/"; source:jar repository:bundle-create
mvn source:jar repository:bundle-create -Dproject.url="http://localhost/";
mvn -Dproject.url=http://localhost/ source:jar repository:bundle-create
mvn source:jar repository:bundle-create -Dproject.url=http://localhost/
But I still get the error message.
Google didn't give me any useful matches when searching for that error
message. :-/
> see
> http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html,
> although a bit too technical.
Thanx! I'll give it a look.
- Steinar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
