>In the moment I have created a schema for the new m2 POM and use it with XML
>Beans for parsing the POM. Before I give the XML to the parser I add a
>science fiction namespace and good ;-)
>
>
If you'd like, you can use the same code Maven does:
maven-model-2.0-alpha-1.jar (you'll also need ple
> From: Brett Porter Sent: Sunday, April 17, 2005 8:14 AM
> To: Maven Developers List
> Subject: Re: POM root Element: project or model?
>
[snip]
> It's planned to provide a generated schema - however, different
> namespaces will not tend to be used inside the POM - we've looked at the
> option
failure to use local snapshots if they don't exist remotely
---
Key: MNG-322
URL: http://jira.codehaus.org/browse/MNG-322
Project: m2
Type: Bug
Components: maven-artifact
Versions: 2.0-alpha-1
Re
Joachim Schreiber wrote:
>The Docs on m2 web site for the POM shows as the root element.
>
>In the m2 cvs is a mixture of and elements in the pom.xml
>files.
>
>
It should be project... it is in the process of being changed. Actually,
either is valid, for now.
>What is the planned name for
The Docs on m2 web site for the POM shows as the root element.
In the m2 cvs is a mixture of and elements in the pom.xml
files.
What is the planned name for this element, project or model?
BTW Why not using a namespace declaration (and an online accessible schema
representation of the pom) i
[ http://jira.codehaus.org/browse/MNG-275?page=comments#action_32102 ]
Brett Porter commented on MNG-275:
--
I'd like to consider making the maven-plugin-api dependency optional, and
review the split between maven-monitor and maven-plugin.
what is prov
[ http://jira.codehaus.org/browse/MNG-275?page=history ]
Brett Porter updated MNG-275:
-
Comment: was deleted
> design and publish the Mojo API
> ---
>
> Key: MNG-275
> URL: http://jira.codehaus.org/browse/MNG-275
[ http://jira.codehaus.org/browse/MNG-275?page=comments#action_32101 ]
Brett Porter commented on MNG-275:
--
I'd like to consider making the maven-plugin-api dependency optional, and
review the split between maven-monitor and maven-plugin.
what is provi
I remember I was going to reply to this :)
Vincent Massol wrote:
>Hi,
>
>2/ Option 2: Generate instrumented sources in target/ somewhere and somehow
>convince the compile plugin to use those sources rather than the ones in
>src/main/java.
>
>
I'd definitely say 2. I don't like the clover:on com
I think the following should be added to the resources section:
value
value
...
The resource patterns can take care of the includes/excludes.
I'm still apprehensive about including filtering at this stage though,
without some way of managing the environment differentiat
>After a checkout from a project I use in Maven 1 the maven-eclipse-plugin to
>generate .classpath and .project. Is this working with the new directory
>structure too?
>
>
>
I'm sure it should all work the same. I know the m2 eclipse plugin is
not yet up to the same functionality as the m1 versi
[ http://jira.codehaus.org/browse/MPTEST-14?page=comments#action_32100 ]
Cyrille Le Clerc commented on MPTEST-14:
This issue seems related to a problem of Jelly that does not redirect
System.out and System.err to Ant Task.
See http://issues.apac
Sorry, I've been pushing them to the maven2 repository because the
converter isn't handling m2 projects in the m1 repository yet.
I'll copy these across on ibiblio, and we can correct later.
- Brett
Emmanuel Venisse wrote:
>Brett,
>
>These dependencies aren't on ibiblio.
>
>
> maven
Yes, I have a JIRA in to turn that into an m2 plugin itself.
Not sure that's exactly what you want, as it forks m2 to run the goals.
Really, an integration test should not be needed - if the plugin is in
Java, you should be able to test with junit. At least up until the point
that multiple goals
Upload wicket-1.0.0-rc2.jar
---
Key: MAVENUPLOAD-362
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-362
Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst
http://wicket.sourceforge.net/downloads/wicket-1.0.0-rc2-bundl
Upload wicket-extensions-1.0.0-rc2.jar
--
Key: MAVENUPLOAD-363
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-363
Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst
http://wicket.sourceforge.net/downloads/
Hi,
I'm writing a Clover plugin and I'd like to write tests for it as I
progress. Obviously most tests will have to be integration tests.
I've seen that the m2 team has developed an integration test system in
maven-components/maven-core-it-verifier with tests in
maven-components/maven-core-it.
[
http://jira.codehaus.org/browse/MPJCOVERAGE-22?page=comments#action_32096 ]
Nate Chadwick commented on MPJCOVERAGE-22:
--
I have the exact same problem with a Spring 1.1.5 unit test. The resource it
is unable to load is in my /src/test/resour
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Saturday, April 16, 2005 4:07 PM
> To: 'Maven Developers List'
> Subject: RE: Maven 2 directory structure for Multiple Modules
> configurable?
[snip]
> It's actually there... (unless I've misunderstood what you meant :-)).
Aahhh I see it
Brett,
These dependencies aren't on ibiblio.
maven
wagon-provider-api
- 1.0-alpha-2-SNAPSHOT
+ 1.0-alpha-3-SNAPSHOT
maven
wagon-http
- 1.0-alpha-2-SNAPSHOT
+ 1.0-alpha-2
maven
wagon-ftp
- 1.0-alpha-2-
> -Original Message-
> From: Joachim Schreiber [mailto:[EMAIL PROTECTED]
> Sent: samedi 16 avril 2005 12:27
> To: dev@maven.apache.org
> Subject: Maven 2 directory structure for Multiple Modules configurable?
[snip]
> +- pom.xml
> +- my-app
> | +- pom.xml
> +- my-webapp
> | +- pom.xml
Joachim Schreiber wrote:
From: Michal Maczka [mailto:[EMAIL PROTECTED]
AFAIK the only limitation which exists in eclipse is that project
directories cannot overlap.
Yes
So you should be able to import to eclipse all projects, which contain
java sources and are "leaves" in the direct
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> AFAIK the only limitation which exists in eclipse is that project
> directories cannot overlap.
Yes
> So you should be able to import to eclipse all projects, which contain
> java sources and are "leaves" in the directory tree.
> So in you case y
Joachim Schreiber wrote:
[...]
Now I read in the Getting Started section of the new Maven 2 documentation
in Subsection Multiple Modules the new plans for creating multiple modules.
I want to ask, is the new directory structure configurable?
+- pom.xml
+- my-app
| +- pom.xml
+- my-webapp
| +- p
[ http://jira.codehaus.org/browse/MAVENUPLOAD-355?page=history ]
Elliotte Rusty Harold closed MAVENUPLOAD-355:
-
Resolution: Fixed
The repository eventually took care of itself automatically. We're now up to
beta 5.
> Upload Jaxen beta
Hi all,
Good to see all these changes in Maven 2.
I use Maven since a long time and actually in a big J2EE project producing a
lot of different artifacts with multi-project. We use Eclipse 3 as IDE and
the maven-eclipse-plugin to create .project and .classpath files. This works
fine for us and tha
[ http://jira.codehaus.org/browse/MNG-320?page=history ]
Brett Porter updated MNG-320:
-
Fix Version: 2.0-alpha-2
can be fixed easily enough. slotting into alpha-2
> .svn files get copied in the generated WAR file
> --
when packaging = pom, the repository should store it in the groupID directory
-
Key: MNG-321
URL: http://jira.codehaus.org/browse/MNG-321
Project: m2
Type: Bug
Components: repository-tools,
.svn files get copied in the generated WAR file
---
Key: MNG-320
URL: http://jira.codehaus.org/browse/MNG-320
Project: m2
Type: Bug
Components: maven-plugins
Versions: 2.0-alpha-1
Reporter: Vincent Massol
29 matches
Mail list logo
