ository or
> the project repository?
I don't remember - what was the rationale for separating the plugin
repository from the main repository?
If the same rationale applies, then i suppose we should use the plugin repo
for site skins as well, unless a separate skin repository would be more
appr
Congratulations on a job well done. :-)
Kind Regards,
John Fallows.
On 10/19/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> We are pleased to announce that Maven 2.0 has been released, and is
> available for download from http://maven.apache.org/maven2/download.html
>
> Maven
til we feel things
have settled down on the 2.0 front.
The element in 2.0.x POM would always contain
2.0.[something]-SNAPSHOT, which would then remove the -SNAPSHOT during
release (when /tags/2.0.[something] is created), and then increment to
2.0.[something + 1]-SNAPSHOT on the 2.0.x branch.
Ok, not going to include much content here. I have a few thoughts, but I
> was hoping to get a varierty of opinions from devs and potential
> contributors about what would work best for them.
Kind Regards,
John Fallows.
--
: Improvement
Components: maven-resources-plugin
Environment: WinXP SP2, Java 1.4.2
Reporter: John Fallows
When filtering is disabled, resources and testResources are not copied
incrementally.
For example, if the target file exists and has a more recent timestamp, the
resource file should not be
: Win XP SP2, Java 1.4.2
Reporter: John Fallows
It seems like there is a collision between dependencies from the same
project but with different classifiers, causing only the main
dependency artifact to be present on the compilation classpath.
project/
api-module/
impl-module/
The api-module
Versions: 2.0-beta-1
Environment: WinXP SP2, Java 1.4.2_06, Maven 2.0-beta-1
Reporter: John Fallows
Attachments: pom.xml
Goals referenced in plugins are executed during the
lifecycle - this is unexpected.
See the attached pom.xml as an example.
Running "m2 install" on this pom
[ http://jira.codehaus.org/browse/MNG-977?page=comments#action_46960 ]
John Fallows commented on MNG-977:
--
Even when plugin groups are no longer required to identify which plugin groups
are present, they should still be available to control the ordering of
Versions: 2.0-beta-1
Reporter: John Fallows
settings.xml has a section to list additional groupIds to search
for top level m2 plugin goals.
By default, "org.apache.maven.plugins" is not required to be present in this
list, and always wins if there is a collision.
that expli
[ http://jira.codehaus.org/browse/MNG-908?page=comments#action_46580 ]
John Fallows commented on MNG-908:
--
This problem seems unrelated to MNG-697 since it does not require the plugin to
access classes from the main project.
> Context class loa
Environment: WinXP SP2, Java 1.4.2, Maven-2.0-beta-1
Reporter: John Fallows
John Fallows wrote:
I am currently developing a custom maven2 plugin that needs to parse
some xml files (using xmlbeans). Therefore I used the m2 xmlbeans
plugin at mojo.codehaus.org to generate the Java code for 3 different
Congratulations to the Apache Maven team - this is a great milestone!
Kind Regards,
John Fallows.
On 9/16/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> The Apache Maven team are proud to announce the beta release of Maven 2.0.
>
> Download it from http://maven.apache.org/maven
[ http://jira.codehaus.org/browse/MNG-823?page=comments#action_46102 ]
John Fallows commented on MNG-823:
--
There is another usecase for sharing context between mojos in the same plugin.
Here is the email sent to Maven Users List.
I'm writing a m
[ http://jira.codehaus.org/browse/MNG-609?page=comments#action_45958 ]
John Fallows commented on MNG-609:
--
In what sense is this a backwards compatibility issue?
I thought that the pom-variables-resolved-during-resource-filtering feature was
added to the
Reporter: John Fallows
Our company uses a home-grown version control system that has it's own
per-directory admin subdirectory, similar in purpose to the administration
subdirectories used by other version control systems, eg. CVS, .svn, etc.
These directories are excluded from processing by de
On 7/25/05, Rafal Krzewski <[EMAIL PROTECTED]> wrote:
> John Fallows wrote:
>
> > Is it always considered a build failure if integration tests do not pass
> > 100%?
>
> I did you mean acceptance tests?
I'm glad you raised this, Rafal. I agree with your des
On 7/20/05, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
> On Wed, 20 Jul 2005, John Fallows wrote:
>
> > On 7/20/05, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> > It seems that classification of these sources into main, test, site,
> > itest, etc, would
On 7/20/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> John Fallows wrote:
>
> >If the PLUGIN-NAME is the plugin artifactId, doesn't this lead to
> >collisions when plugins only differ by groupId?
> >
> >
> It's actually whatever the plugin wants to
test/
java/
resources/
target/
generated-src/
main/
java/
resources/
test/
java/
resources/
etc.
One obvious answer is to avoid collisions, but I'm not sure that
matters if all the various generated sources nee
: Maven 2
Type: Bug
Versions: 2.0-alpha-3
Environment: Maven 2.0-alpha-3, WinXP SP2, Java 1.5.0_02
Reporter: John Fallows
I noticed that the latest code on the trunk adds support for filtered
resources, including the ability to refer to pom properties, in addition to any
filter
Reporter: John Fallows
m2 deploy does not include RELEASE information by default.
Presumably this works as designed to avoid accidental release
publishing during nightly build deployment?
m2 -DupdateReleaseInfo=true deploy breaks on first deploy with a
FileNotFoundException.
--
This message
Versions: 2.0-alpha-3
Environment: Maven 2.0-alpha-3, WinXP SP2, Java 1.5.0_02
Reporter: John Fallows
I just noticed a NPE in the Maven2 Javadoc Report that occurs when
... is not present in the POM.
Also, it does not seem to matter if the parent POM has the
..., the NPE still occurs.
--
This
ngines
for integration testing, including junit.
According to the above feedback then, the cactus integration tests
would reside in either src/test/cactus or src/itest/cactus.
[snip]
Kind Regards,
John Fallows.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNG-583?page=comments#action_42817 ]
John Fallows commented on MNG-583:
--
It is possible to workaround the missing project.addResourceRoot(String) with
the following code.
String resourceRoot = ...;
List resources
Environment: Maven 2.0-alpha-3, WinXP SP2, Java 1.5.0_02
Reporter: John Fallows
Currently, there is no way to supply a custom ruleset for the
maven-checkstyle-plugin.
A custom ruleset is likely to span multiple projects, and it doesn't make sense
to duplicate the custom ruleset fi
Versions: 2.0-alpha-3
Environment: Maven 2.0-alpha-3, WinXP SP2, Java 1.5.0_02
Reporter: John Fallows
Please add something equivalent to MavenProject.addResourceRoot(String) and
MavenProject.addTestResourceRoot(String) to allow plugins to dynamically
include generated resources that can be
Environment: Maven 2.0-alpha-3, Java 1.5.0_02, WinXP SP2
Reporter: John Fallows
When is present in pom.xml with "pom" packaging,
then the last plugin artifact information (groupId, artifactId,
version) is used during m2 install.
4.0.0
org.example
sample
al
Versions: 2.0-alpha-3
Environment: WinXP SP2, Java 1.5, Maven 2.0-alpha3
Reporter: John Fallows
Consider the case where two elements are present in pom.xml,
and a particular plugin is being stored in the second plugin repository.
During a build, say m2 install, plugin versions are
If processContents was set to "skip", the would validate,
but that seems very lenient.
If "war" was defined as a namespace prefix, then:
...
would validate just fine. (Note. war-colon-bundle, not war-period-bundle).
If you changed the style of
ments at each nested level within the document.
This gives greater flexibility during editing, without sacrificing
correctness.
Kind Regards,
John Fallows.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
ted sources?
For example:
src
src/main
src/main/java
src/main/resources
target
target/src
target/src/main
target/src/main/java
target/src/main/resources
This would be convenient for plugin developers who are writing for the
"generate-sources" m2 lifecycle
31 matches
Mail list logo
