new version of this dependency.
Has anybody else ran into this?
I did a little bit of digging and it looks like it is removing the
dependency from the model and replacing it with the nested dependencies in
the DefaultModelBuilder when it resolves the dependencies. Is this by
design?
Thank you,
Kurt Zettel
Hello Maven Developers,
I have built a plugin that builds projects for the BlackBerry. It
needs to build for multiple RIM OS versions so I use a classifier such
as my-library-1.0-rim-4.5.0, my-library-1.0-rim-5.0.0 etc. I am
running into two problems:
1. How can I resolve this classifier recurs
you,
Kurt Zettel
On Sun, May 22, 2011 at 2:19 PM, Kurt Zettel II wrote:
> Hello Maven Developers,
>
> I am using the maven-plugin-test-harness-2.0-alpha-1 and creating JUnit
> tests for a plugin I am developing. I am able to test my Mojos but I am
> currently hardcoding some val
there an easy or standard
way to have my JUnit tests read my settings.xml so that my JUnit tests are
not as environment dependent? At a minimum I would like to read
properties. Ideally I would like to activate a profile and then read
properties.
Thank you,
Kurt Zettel
The jars were in two different groups. We are
using: plexus:plexus-log4j-logging:1.0 which imports an old version of the
plexus-container which is in the group plexus versus org.codehaus.plexus.
--
Kurt
On Wed, May 5, 2010 at 2:44 PM, Benjamin Bentmann wrote:
> Kurt Zettel wrote:
>
you,
Kurt
On Mon, May 3, 2010 at 5:11 PM, Kurt Zettel wrote:
> I have a custom plugin which
> implements
> org.codehaus.plexus.personality.plexus.lifecycle.phase.Contextualizable.
> It has been working fine with the older alphas (5 and 6) but with alpha-7
> and beta-1 my plug
thoughts on what changed or
what I could be doing wrong?
Thank you,
--
Kurt Zettel, Chief Architect
Metova, Inc.
handler.
On Wed, Jan 27, 2010 at 1:04 PM, Brett Porter wrote:
> Try the latest 2.0-SNAPSHOT of the plugin, this should be fixed now.
>
> - Brett
>
> On 28/01/2010, at 4:29 AM, Kurt Zettel wrote:
>
> > I developed a plugin and integration tested it using using Maven 3. On
plugin
(which worked fine with Maven 2.2.1) but it is giving me problems with Maven
3.0 alpha 6. Any advice on where to look in the code to fix this problem?
Thank you,
Kurt Zettel
; Look at any of the core plugins and the ITs that Benjamin has created
> there. Most of them have ITs now and they use the invoker plugin which is
> what we use in the Maven ITs as well.
>
> https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-shade-plugin
>
> On 2009-12-12,
/plugin-developers/plugin-testing.html. Is there an
updated page on creating this sort of test or an example I can follow of how
I can run these tests with the updated Maven version? Are any existing
plugins testing using this method?
Thank You,
Kurt Zettel
11 matches
Mail list logo
