Re: Maven JavaScript Plugin
We're using it at my workplace. We have our own "released' version just to stop the plugin update check from happening so frequently. I think the plugin is strong for creating javascript artifacts and keeping them separate. If you pair it with the jetty-maven-plugin, you can get away with a pure-javascript-development environment pretty easily. We do not use the jsunit integration, and I would recommend only reserving that for integration testing, as the bootstrap to start a browser can be slow. The minification/combination of artifacts is great. We're using maven to manage 4 different JS libraries and combine them all in our final product. Hope that helps! - Josh On Thu, Oct 22, 2009 at 5:09 PM, Neil Chaudhuri < nchaudh...@potomacfusion.com> wrote: > A colleague at work expressed an interest in doing a lot of Maven-like > things in the JavaScript realm. I did some research and discovered the Maven > JavaScript plugin. It looks neat, but it is an alpha version and seems to > have little activity. > > I was simply hoping to find some comments from those who have investigated > or used the Maven JavaScript plugin. Does it work? Strengths and weaknesses? > Any insight is appreciated. > > Thanks. > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Re: maven scala plugin troubles -- scalac compiler plugin
It's used in several locations. Anyway, your fix is committed on the
master. I'm working on adding support for transitive dependencies now.
- Josh
On Wed, Jul 22, 2009 at 10:49 PM, Nicholas Tung wrote:
> On Wed, Jul 22, 2009 at 7:00 PM, Josh Suereth wrote:
>
>> Hey, I just go this email. I'll make the patch and commit shortly.
>> Thanks for the submission!
>>
>> There's still some mismatch since we re-built the scala-tools.org server,
>> so the maven-scala-plugin nightlies are not getting published. I'm going to
>> try to resolve that shortly.
>>
>> - Josh
>
>
> Thanks very much! Please adjust the code style as you see fit. I'm not sure
> whether it's worth reusing the addToClasspath() call, if it's just creating
> a Set and adding a single element to it.
>
> regards,
> Nicholas
>
>
>>
>>
>> On Wed, Jul 22, 2009 at 4:14 PM, Nicholas Tung wrote:
>>
>>> The problem is that my scala plugin project has additional dependencies.
>>> These are added to pluginClassPath, but then you only add the first element
>>> from pluginClassPath (why the first? this seems a bit arbitrary).
>>>
>>> If you wouldn't mind fixing this (in github master), I'd appreciate it
>>> very much. I don't think users would ever want to add deps of the project as
>>> plugins, so perhaps the changes below would work.
>>>
>>> Also, is the latest version on a public site?
>>>
>>> regards,
>>> Nicholas
>>> https://ntung.com
>>>
>>> +protected void addToClasspath(BasicArtifact artifact_info,
>>> +Set classpath, boolean add_deps) throws Exception
>>> +{
>>> +addToClasspath(factory.createArtifact(artifact_info.groupId,
>>> +artifact_info.artifactId, artifact_info.version,
>>> +Artifact.SCOPE_RUNTIME, "jar"), classpath, add_deps);
>>> +}
>>>
>>> +protected void addToClasspath(Artifact artifact, Set
>>> classpath,
>>> +boolean add_deps) throws Exception
>>> +{
>>> resolver.resolve(artifact, remoteRepos, localRepo);
>>> classpath.add(artifact.getFile().getCanonicalPath());
>>> -for(Artifact dep: resolveArtifactDependencies(artifact)) {
>>> -classpath.add(dep.getFile().getCanonicalPath());
>>> +if (add_deps) {
>>> +for (Artifact dep : resolveArtifactDependencies(artifact)) {
>>> +classpath.add(dep.getFile().getCanonicalPath());
>>> +}
>>> }
>>> }
>>>
>>> +/**
>>> + * Retrieves a list of paths to scala compiler plugins.
>>> + * @return The list of plugins
>>> + * @throws Exception
>>> + */
>>> +private Set getCompilerPlugins() throws Exception {
>>> +Set plugins = new HashSet();
>>> +if (compilerPlugins != null) {
>>> +Set ignoreClasspath = new HashSet();
>>> +addToClasspath(SCALA_GROUPID, "scala-compiler",
>>> scalaVersion,
>>> +ignoreClasspath);
>>> +addToClasspath(SCALA_GROUPID, SCALA_LIBRARY_ARTIFACTID,
>>> +scalaVersion, ignoreClasspath);
>>> +for (BasicArtifact artifact : compilerPlugins) {
>>> +System.out.println("compiler plugin: " +
>>> artifact.toString());
>>> +// TODO - Ensure proper scala version for plugins
>>> +Set pluginClassPath = new HashSet();
>>> +addToClasspath(artifact, pluginClassPath, false);
>>> +pluginClassPath.removeAll(ignoreClasspath);
>>> +plugins.addAll(pluginClassPath);
>>> +}
>>> +}
>>> +return plugins;
>>> +}
>>>
>>>
>>> On Wed, Jul 22, 2009 at 12:43 PM, Nicholas Tung
>>> wrote:
>>>
>>>> It looks like you're setting this stuff with javadoc... imho, an
>>>> attribute is a bit more robust. Also, you have
>>>>
>>>>
>>>> instead of , but changing it doesn't
>>>> seem to help (it then compiles without any plugin).
>>>>
>>>> If you could point me to other relevant code (I'm looking at
>>>> ScalaMojoSupport.java), that would be much appreciated.
>>>>
>
Re: maven scala plugin troubles -- scalac compiler plugin
Hey, I just go this email. I'll make the patch and commit shortly. Thanks
for the submission!
There's still some mismatch since we re-built the scala-tools.org server, so
the maven-scala-plugin nightlies are not getting published. I'm going to
try to resolve that shortly.
- Josh
On Wed, Jul 22, 2009 at 4:14 PM, Nicholas Tung wrote:
> The problem is that my scala plugin project has additional dependencies.
> These are added to pluginClassPath, but then you only add the first element
> from pluginClassPath (why the first? this seems a bit arbitrary).
>
> If you wouldn't mind fixing this (in github master), I'd appreciate it very
> much. I don't think users would ever want to add deps of the project as
> plugins, so perhaps the changes below would work.
>
> Also, is the latest version on a public site?
>
> regards,
> Nicholas
> https://ntung.com
>
> +protected void addToClasspath(BasicArtifact artifact_info,
> +Set classpath, boolean add_deps) throws Exception
> +{
> +addToClasspath(factory.createArtifact(artifact_info.groupId,
> +artifact_info.artifactId, artifact_info.version,
> +Artifact.SCOPE_RUNTIME, "jar"), classpath, add_deps);
> +}
>
> +protected void addToClasspath(Artifact artifact, Set
> classpath,
> +boolean add_deps) throws Exception
> +{
> resolver.resolve(artifact, remoteRepos, localRepo);
> classpath.add(artifact.getFile().getCanonicalPath());
> -for(Artifact dep: resolveArtifactDependencies(artifact)) {
> -classpath.add(dep.getFile().getCanonicalPath());
> +if (add_deps) {
> +for (Artifact dep : resolveArtifactDependencies(artifact)) {
> +classpath.add(dep.getFile().getCanonicalPath());
> +}
> }
> }
>
> +/**
> + * Retrieves a list of paths to scala compiler plugins.
> + * @return The list of plugins
> + * @throws Exception
> + */
> +private Set getCompilerPlugins() throws Exception {
> +Set plugins = new HashSet();
> +if (compilerPlugins != null) {
> +Set ignoreClasspath = new HashSet();
> +addToClasspath(SCALA_GROUPID, "scala-compiler", scalaVersion,
> +ignoreClasspath);
> +addToClasspath(SCALA_GROUPID, SCALA_LIBRARY_ARTIFACTID,
> +scalaVersion, ignoreClasspath);
> +for (BasicArtifact artifact : compilerPlugins) {
> +System.out.println("compiler plugin: " +
> artifact.toString());
> +// TODO - Ensure proper scala version for plugins
> +Set pluginClassPath = new HashSet();
> +addToClasspath(artifact, pluginClassPath, false);
> +pluginClassPath.removeAll(ignoreClasspath);
> +plugins.addAll(pluginClassPath);
> +}
> +}
> +return plugins;
> +}
>
>
> On Wed, Jul 22, 2009 at 12:43 PM, Nicholas Tung wrote:
>
>> It looks like you're setting this stuff with javadoc... imho, an attribute
>> is a bit more robust. Also, you have
>>
>>
>> instead of , but changing it doesn't
>> seem to help (it then compiles without any plugin).
>>
>> If you could point me to other relevant code (I'm looking at
>> ScalaMojoSupport.java), that would be much appreciated.
>>
>> Thanks in advance,
>> Nicholas
>> https://ntung.com
>>
>> On Wed, Jul 22, 2009 at 12:12 PM, Nicholas Tung
>> wrote:
>>
>>> Hi Josh,
>>>
>>> Thanks; the repo is at [1], and I've attached the plugin (though I
>>> suspect it has more to do with command line compilation rather than the
>>> plugin itself).
>>>
>>> I might end up overriding the main compiler class (i.e. not
>>> scala.tools.nsc.Main), so I could probably hack something from there.
>>>
>>> I got github master to build... if you could tell me where things
>>> are, I'd appreciate it.
>>>
>>> regards,
>>> Nicholas
>>> https://ntung.com
>>>
>>> [1] http://github.com/gatoatigrado/skalch/tree/master
>>>
>>>
>>> On Wed, Jul 22, 2009 at 8:34 AM, Josh Suereth
>>> wrote:
>>>
>>>> Does your scalac plugin depend on any other plugins? If you can point
>>>> me towards a repository holding your scalac plugin, I can create an
>>>> integration test for this use case. I'm adding it to the list of known
>>>> issues.
>>>
Re: maven scala plugin troubles -- scalac compiler plugin
Does your scalac plugin depend on any other plugins? If you can point me towards a repository holding your scalac plugin, I can create an integration test for this use case. I'm adding it to the list of known issues. - Josh On Wed, Jul 22, 2009 at 2:43 AM, Nicholas Tung wrote: > Hi David and Josh, > >I'm having some trouble with the maven scala plugin; it doesn't seem to > be setting the -Xplugin line correctly when I try to build a project [1]. > The configuration passed to the maven-scala-plugin is [2]. I'm running $(mvn > install -Dmaven.scala.displayCmd=true). > > Feel free to look at the pom.xml files if you want [3], but don't feel > obliged... I haven't done proper Scala / Java separation yet (among other > things to clean it up). > > Thanks so much! > Nicholas > https://ntung.com > > [1] > version 2.10 gives > > -Xplugin:/home/gatoatigrado/.m2/repository/org/scala-tools/maven-scala-plugin/2.10/maven-scala-plugin-2.10.jar > > version 2.11 gives > -Xplugin:/home/gatoatigrado/.m2/repository/xom/xom/1.1/xom-1.1.jar > > the correct version should be > -Xplugin:/home/gatoatigrado/.m2/repository/edu/berkeley/cs/sketch/skalch-plugin/git-master/skalch-plugin-git-master.jar > > > [2] > > edu.berkeley.cs.sketch > skalch-plugin > git-master > > > [3] http://github.com/gatoatigrado/skalch/tree/master >
Maven 2.1.0 + SHITTY plugin => Whose issue, Mine, Yours, Theirs?
All, I just upgraded to Maven 2.1.0 and I"m getting the following error in the integration test logs when running my "Super Helpful Integration Testing ThingY" (SHITTY) integration tests - OUT: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager getting plugin 'org.scala-tools:maven-scala-plugin': Plugin 'org.scala-tools:maven-scala-plugin:testing' has an invalid descriptor: OUT: 1) Plugin's descriptor contains the wrong version: 2.10.1 OUT:at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1521) I'm guessing maven 2.1.0 is performing some new check that the shitty plugin hasn't been updated for? As a temporary work-around I can just develop in maven 2.0.10 for now, however I was wondering if 1) This is actually an issue with the shitty plugin, or I've failed to configure things correctly 2) I should be using some other form of integration testing for maven 2.1.0 3) if anyone else has seen this issue? Thanks for the help! Maven 2.1.0 is working great for all my other projects that use the maven-scala-plugin, just not the plugin itself. Great work Maven Team -Josh
Maven-bundle-plugin & Scala
Apache Felix Users - I'm currently working om a scalac (the scala compiler) plugin that enforces all package imports within a scala "module" either come from that module or are exported by another module on its classpath. I'd like to integrate into the "bundle" lifecycle. Currently, for jar/war projects, the maven-scala-plugin executes before the maven-compiler-plugin (generating .class files for the .scala files and simply parsing the .java), then the maven-compiler plugin handles the actual .java compilation and the whole lifecycle is happy. Is this approach feasible for integration with the maven-bundle-plugin? Thanks!! -Josh Suereth
Re: mvn eclipse:eclipse not adding source directories
Thanks for the answer! I'll notify the users. Anyway to integrate the eclipse + scala plugins directly? On Fri, Feb 13, 2009 at 4:44 AM, Dirk Olmes wrote: > Josh Suereth wrote: > > Hey guys, > > > > I'm trying to better integrate the maven-eclipse-plugin with the > > maven-scala-plugin. Is there anyway I can notify the eclipse:eclipse > goal > > to add extra source directories when creating the eclipse project files? > > Use the build-helper plugin from Codehaus [0] to add additional source > directories and the eclipse plugin will pick them up. > > [0] http://mojo.codehaus.org/build-helper-maven-plugin/ > > HTH, > > -dirk > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
mvn eclipse:eclipse not adding source directories
Hey guys, I'm trying to better integrate the maven-eclipse-plugin with the maven-scala-plugin. Is there anyway I can notify the eclipse:eclipse goal to add extra source directories when creating the eclipse project files? Thanks! -Josh
Re: pde-maven-plugin
I gotta say, I'm *VERY* excited about Tycho. On Thu, Jan 8, 2009 at 11:43 AM, Eugene Kuleshov wrote: > > > PDE plugin is bit outdated and I don't think it supports Eclipse 3.4. > > There is another plugin that can be used to handle building of Eclipse > plugins and it works with Eclipse 3.3. and 3.4. There is some initial > documentation on the wiki at > http://docs.codehaus.org/display/M2ECLIPSE/Tycho+project+overview > > regards, > Eugene > > > > sandraB wrote: > > > > Hi, > > I try to use the pde-maven-plugin to generate a HelloWorld plugin > eclipse. > > I already succeed for the eclipse 3.2 and eclipse 3.3 version but I've > got > > an issue with eclipse 3.4. > > > > > > [WARNING] Attempting to build MavenProject instance for Artifact > > (org.codehaus.mojo:pde-maven-plugin:1.0-alpha-2-20070917.003805-1) of > > type: maven-plugin; constructing POM artifact instead. > > [INFO] [pde:ext] > > [INFO] Startup jar found at: > > > D:\sandra\appli\eclipse\3.4.1\plugins\org.eclipse.equinox.launcher.source_1.0.101.R34x_v20080819.jar > > [INFO] java -classpath > > > D:\sandra\appli\eclipse\3.4.1\plugins\org.eclipse.equinox.launcher.source_1.0.101.R34x_v20080819.jar > > org.eclipse.equinox.launcher.Main -application > > org.eclipse.ant.core.antRunner -buildfile > > D:\sandra\Projets\3.4.1\plugins\helloWorld2\target\pdeBuilder\build.xml > > java.lang.NoClassDefFoundError: org/eclipse/equinox/launcher/Main > > Caused by: java.lang.ClassNotFoundException: > > org.eclipse.equinox.launcher.Main > > > > Could you help me to solve this issue ? > > Thanks in advance > > > > -- > View this message in context: > http://www.nabble.com/pde-maven-plugin-tp21354325p21355564.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: MAVEN certifications
Here's a fun one for you: http://letmegooglethatforyou.com/?q=jfgi Combines the indirectly and directly rude methods of suggesting someone performs their own search before pegging the list-serve. On Tue, Dec 16, 2008 at 2:50 PM, Wayne Fay wrote: > > Just out of curiosity, why is this your new favorite site? So to take > this > > off topic, but I saw this and wonder where the use case for this site is? > i > > think I might be missing something > > LetMeGoogleThatForYou.com provides a means of teaching someone how to > use Google, in case they don't already know. It is a (mildly rude) way > of (indirectly) reprimanding someone when they ask a question that can > easily be answered without asking someone else, while still answering > the question they asked. > > The best use of the site I've seen lately was someone on this list > asking for the definition of "modicum" after I used that word in an > email. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: How to mkdir and move files as part of build
http://letmegooglethatforyou.com/?q=modicum On Fri, Dec 12, 2008 at 10:52 PM, CheapLisa wrote: > > yea, I already googled. I already to that before posting. Nothing came > up. > What does "modicum" mean? > > thanks > > > > Wayne Fay wrote: > > > >> Somebody made me discover that recently: http://tinyurl.com/62f6ku ... > >> > >> No offense, week-end is coming :-). > >> Cheers > > > > So long as "CheapLisa" continues sending emails like this without > > doing even a modicum of her own reading/research, I think she's going > > to have to accept an increasingly less than polite tone in the > > responses. Especially on a Friday afternoon. ;-) > > > > This list is pretty tolerant and largely flame-free, but we respond > > much better to people who have done their homework (and Googling) > > before asking questions that are very clearly answered with 5 minutes > > of self-help before asking someone in the community to do their > > work/searching for them... > > > > Wayne > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > -- > View this message in context: > http://www.nabble.com/How-to-mkdir-and-move-files-as-part-of-build-tp20983063p20987174.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Is Maven / JUnit 4.x broken (annotations)
What I'm saying is that the surefire plugin is responsible for bootstrapping Junit4, but does not follow all of its conventions. It has its own conventions. If you want to use Junit4 in maven, that means you use surefire to call into Junit4. If you don't like the default configuration for the surefire plugin, feel free to override it in a parent pom (and all your children will make use of it). Here's the relevant section of the surefire plugin website: http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.html On Fri, Dec 12, 2008 at 11:02 PM, CheapLisa wrote: > > What does group-a and artifact-a refer to? > > so I have to do this in every pom in every sub-module? Is there anything I > can do in the top level pom that will take care of the whole project? > > What you are saying is that the surefire plugin is not JUnit4 enabled? > > thanks > > CL > > > > mgainty wrote: > > > > > > place the groupId/artifactId/version in the dependencies in > > dependencyManagement Section of the parent pom > > > > ... > > > > > > > > group-a > > artifact-a > > 1.0 > > > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > > > > hth > > Martin > > __ > > Disclaimer and confidentiality note > > Everything in this e-mail and any attachments relates to the official > > business of Sender. This transmission is of a confidential nature and > > Sender does not endorse distribution to any party other than intended > > recipient. Sender does not necessarily endorse content contained within > > this transmission. > > > > > > > > > >> Date: Wed, 10 Dec 2008 12:44:45 -0800 > >> From: l...@purpleblade.net > >> To: users@maven.apache.org > >> Subject: Re: Is Maven / JUnit 4.x broken (annotations) > >> > >> > >> I looked at my effective pom. I have a dependency there on JUnit 4.5. > >> The only reference to surefire was maven-surefire-reports-plugin in the > >> reporting section. > >> > >> how do I know that surefire is using my dependency of JUnit 4.5? Is > >> maven > >> bundled with another version of JUnit and using an earlier version that > >> I'm > >> not aware of? > >> > >> How do I force the surefire plugin to use JUnit 4.5? > >> > >> thanks > >> > >> L > >> > >> > >> > >> John Stoneham wrote: > >> > > >> >>> On Wed, Dec 10, 2008 at 12:16 AM, CheapLisa > >> >>> wrote: > >> I have JUnit 4.5 as a dependency in my maven pom > >> and I have imported annotations into my test case but > >> it is not recognizing the @Test and @Ignore annotations. > >> > >> I still have to preface the method name with "test" > >> and the @Ignore tests get executed. > >> > >> Is something broken? What do I need to do to get this > >> to work like expected and to take advantage of JUnit 4.x > >> which has over a year of release now. > >> > > >> > Hm. Last time this happened to me it was because I was trying to > >> > repackage JUnit with a bunch of other things, and it turned out > >> > surefire was inspecting my POM to look for a junit:junit dependency, > >> > then pulling the version off that to determine whether to look for > >> > JUnit 4 tests. > >> > > >> > Sounds to me like surefire thinks your JUnit dependency is version 3. > >> > We've got JUnit 4.4 configured here and it runs both 3- and 4-style > >> > tests properly. > >> > > >> > Is it possible to post the output of mvn help:effective-pom here? > >> > > >> > - John > >> > > >> > - > >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: users-h...@maven.apache.org > >> > > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://www.nabble.com/Is-Maven---JUnit-4.x-broken-%28annotations%29-tp20929389p20943444.html > >> Sent from the Maven - Users mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > > > > _ > > Send e-mail faster without improving your typing skills. > > > http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008 > > > > -- > View this message in context: > http://www.nabble.com/Is-Maven---JUnit-4.x-broken-%28annotations%29-tp20929389p20987238.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven plugin problem (can not solve after many tries)
A few questions:
1) Is your project supposed to be a "pom" project
2) What's in your parent pom?
3) What are you calling on the maven command line?
It's looking for 'org.apache.maven.plugins:maven-izpack-plugin, which is the
old maven 1 version. So you either have that specified somewhere, or you're
using the command line incorrectly.
On Thu, Dec 11, 2008 at 6:37 PM, CheapLisa wrote:
>
>
>
> I am getting this error message:
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
> 'org.apache.maven.plugins:maven-i
> zpack-plugin' does not exist or no valid version could be found
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor
>
> ---
> this is my pom.xml that includes the maven plugin - any ideas? Everything
> looks correct to me.
>
> xmlns="http://maven.apache.org/POM/4.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
>
>
>com.acme
>izpack.parent-pom
>1.0
>
>
>com.acme
>izpack-maven-plugin
>2.1.0
>Amp Patch (izpack)
>pom
>
>
>
>
>
>org.izpack
>izpack
>4.1.1
>
>true
>
>
>
>
>
>package
>
>
>
>
>
>org.apache.maven.plugins
>maven-antrun-plugin
>1.3
>
>
>
>
>
>
>
>
>
>
>
>create-staging-area
>process-resources
>
>
>run
>
>
>
>
>
>
>
>
> org.codehaus.izpack
> izpack-maven-plugin
> 1.0-alpha-4
>
>
>
>${staging.dir}
>
>
>
>
> standard-installer
> package
>
>izpack
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>${project.build.directory}/staging
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/maven-plugin-problem-%28can-not-solve-after-many-tries%29-tp20964990p20964990.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: Is Maven / JUnit 4.x broken (annotations)
Also to follow that up, Although you didn't specify the maven-surefire-plugin, your build file has inherited it from the ethereal "maven super pom". Type mvn help:effective-pom to see what your pom *really* looks like, so you can get an idea of how/what to configure for surefire. On Thu, Dec 11, 2008 at 7:46 PM, Josh Suereth wrote: > Lisa, > > > The answer is that although Junit4 might support finding the @Test > annotations, the maven surefire plugin (being backwards compatable, AND a > completely different tool) looks for Test* *Test and *TestSuite. You need > to configure the maven-surefire-plugin (This is the part of maven that calls > into junit) for junit4 conventions, or you won't get your desired behavior. > > -Josh > > > On Thu, Dec 11, 2008 at 6:39 PM, CheapLisa wrote: > >> >> I do not believe this has anything to do with it and I don't understand >> what >> you are saying. >> >> L >> >> >> >> mgainty wrote: >> > >> > >> > place the groupId/artifactId/version in the dependencies in >> > dependencyManagement Section of the parent pom >> > >> > ... >> > >> > >> > >> > group-a >> > artifact-a >> > 1.0 >> > >> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html >> > >> > hth >> > Martin >> > __ >> > Disclaimer and confidentiality note >> > Everything in this e-mail and any attachments relates to the official >> > business of Sender. This transmission is of a confidential nature and >> > Sender does not endorse distribution to any party other than intended >> > recipient. Sender does not necessarily endorse content contained within >> > this transmission. >> > >> > >> > >> > >> >> Date: Wed, 10 Dec 2008 12:44:45 -0800 >> >> From: l...@purpleblade.net >> >> To: users@maven.apache.org >> >> Subject: Re: Is Maven / JUnit 4.x broken (annotations) >> >> >> >> >> >> I looked at my effective pom. I have a dependency there on JUnit 4.5. >> >> The only reference to surefire was maven-surefire-reports-plugin in the >> >> reporting section. >> >> >> >> how do I know that surefire is using my dependency of JUnit 4.5? Is >> >> maven >> >> bundled with another version of JUnit and using an earlier version that >> >> I'm >> >> not aware of? >> >> >> >> How do I force the surefire plugin to use JUnit 4.5? >> >> >> >> thanks >> >> >> >> L >> >> >> >> >> >> >> >> John Stoneham wrote: >> >> > >> >> >>> On Wed, Dec 10, 2008 at 12:16 AM, CheapLisa >> >> >>> wrote: >> >> >>>> I have JUnit 4.5 as a dependency in my maven pom >> >> >>>> and I have imported annotations into my test case but >> >> >>>> it is not recognizing the @Test and @Ignore annotations. >> >> >>>> >> >> >>>> I still have to preface the method name with "test" >> >> >>>> and the @Ignore tests get executed. >> >> >>>> >> >> >>>> Is something broken? What do I need to do to get this >> >> >>>> to work like expected and to take advantage of JUnit 4.x >> >> >>>> which has over a year of release now. >> >> > >> >> > Hm. Last time this happened to me it was because I was trying to >> >> > repackage JUnit with a bunch of other things, and it turned out >> >> > surefire was inspecting my POM to look for a junit:junit dependency, >> >> > then pulling the version off that to determine whether to look for >> >> > JUnit 4 tests. >> >> > >> >> > Sounds to me like surefire thinks your JUnit dependency is version 3. >> >> > We've got JUnit 4.4 configured here and it runs both 3- and 4-style >> >> > tests properly. >> >> > >> >> > Is it possible to post the output of mvn help:effective-pom here? >> >> > >> >> > - John >> >> > >> >> > - >> >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> >> > For additional commands, e-mail: users-h...@maven.apache.org >> >> > >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Is-Maven---JUnit-4.x-broken-%28annotations%29-tp20929389p20943444.html >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >> > >> > _ >> > Send e-mail faster without improving your typing skills. >> > >> http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008 >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Is-Maven---JUnit-4.x-broken-%28annotations%29-tp20929389p20964992.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >
Re: Is Maven / JUnit 4.x broken (annotations)
Lisa, The answer is that although Junit4 might support finding the @Test annotations, the maven surefire plugin (being backwards compatable, AND a completely different tool) looks for Test* *Test and *TestSuite. You need to configure the maven-surefire-plugin (This is the part of maven that calls into junit) for junit4 conventions, or you won't get your desired behavior. -Josh On Thu, Dec 11, 2008 at 6:39 PM, CheapLisa wrote: > > I do not believe this has anything to do with it and I don't understand > what > you are saying. > > L > > > > mgainty wrote: > > > > > > place the groupId/artifactId/version in the dependencies in > > dependencyManagement Section of the parent pom > > > > ... > > > > > > > > group-a > > artifact-a > > 1.0 > > > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > > > > hth > > Martin > > __ > > Disclaimer and confidentiality note > > Everything in this e-mail and any attachments relates to the official > > business of Sender. This transmission is of a confidential nature and > > Sender does not endorse distribution to any party other than intended > > recipient. Sender does not necessarily endorse content contained within > > this transmission. > > > > > > > > > >> Date: Wed, 10 Dec 2008 12:44:45 -0800 > >> From: l...@purpleblade.net > >> To: users@maven.apache.org > >> Subject: Re: Is Maven / JUnit 4.x broken (annotations) > >> > >> > >> I looked at my effective pom. I have a dependency there on JUnit 4.5. > >> The only reference to surefire was maven-surefire-reports-plugin in the > >> reporting section. > >> > >> how do I know that surefire is using my dependency of JUnit 4.5? Is > >> maven > >> bundled with another version of JUnit and using an earlier version that > >> I'm > >> not aware of? > >> > >> How do I force the surefire plugin to use JUnit 4.5? > >> > >> thanks > >> > >> L > >> > >> > >> > >> John Stoneham wrote: > >> > > >> >>> On Wed, Dec 10, 2008 at 12:16 AM, CheapLisa > >> >>> wrote: > >> I have JUnit 4.5 as a dependency in my maven pom > >> and I have imported annotations into my test case but > >> it is not recognizing the @Test and @Ignore annotations. > >> > >> I still have to preface the method name with "test" > >> and the @Ignore tests get executed. > >> > >> Is something broken? What do I need to do to get this > >> to work like expected and to take advantage of JUnit 4.x > >> which has over a year of release now. > >> > > >> > Hm. Last time this happened to me it was because I was trying to > >> > repackage JUnit with a bunch of other things, and it turned out > >> > surefire was inspecting my POM to look for a junit:junit dependency, > >> > then pulling the version off that to determine whether to look for > >> > JUnit 4 tests. > >> > > >> > Sounds to me like surefire thinks your JUnit dependency is version 3. > >> > We've got JUnit 4.4 configured here and it runs both 3- and 4-style > >> > tests properly. > >> > > >> > Is it possible to post the output of mvn help:effective-pom here? > >> > > >> > - John > >> > > >> > - > >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: users-h...@maven.apache.org > >> > > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://www.nabble.com/Is-Maven---JUnit-4.x-broken-%28annotations%29-tp20929389p20943444.html > >> Sent from the Maven - Users mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > > > > _ > > Send e-mail faster without improving your typing skills. > > > http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008 > > > > -- > View this message in context: > http://www.nabble.com/Is-Maven---JUnit-4.x-broken-%28annotations%29-tp20929389p20964992.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Is Maven / JUnit 4.x broken (annotations)
I believe the name of the class still matters. Try calling it "Test*.java" On Wed, Dec 10, 2008 at 12:16 AM, CheapLisa <[EMAIL PROTECTED]> wrote: > > I have JUnit 4.5 as a dependency in my maven pom > and I have imported annotations into my test case but > it is not recognizing the @Test and @Ignore annotations. > > I still have to preface the method name with "test" > and the @Ignore tests get executed. > > Is something broken? What do I need to do to get this > to work like expected and to take advantage of JUnit 4.x > which has over a year of release now. > > > thanks > > Lisa > -- > View this message in context: > http://www.nabble.com/Is-Maven---JUnit-4.x-broken-%28annotations%29-tp20929389p20929389.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Maven Jaxb plugin?
In the past I've used the maven-exec-plugin with xbeans. Not sure if that helps. On Dec 9, 2008, at 1:31 PM, CheapLisa <[EMAIL PROTECTED]> wrote: Another question, is there a maven2 plugin that will generate an XSD from XML ? thanks Lisa Adam Leggett wrote: Try http://mojo.codehaus.org/jaxb2-maven-plugin/index.html For example: org.codehaus.mojo jaxb2-maven-plugin xjc com.acme -Original Message- From: CheapLisa [mailto:[EMAIL PROTECTED] Sent: 09 December 2008 16:33 To: users@maven.apache.org Subject: Maven Jaxb plugin? I searched for a maven jaxb plugin and found xjc-maven-plugin but it is not documented. Does anyone have an example of generating an xsd from xml and then the java objects from xsd? Does anyone know why this plugin is not documented? -- View this message in context: http://www.nabble.com/Maven-Jaxb-plugin--tp20918118p20918118.html Sent from the Maven - Users mailing list archive at Nabble.com. - 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] -- View this message in context: http://www.nabble.com/Maven-Jaxb-plugin--tp20918118p20920625.html Sent from the Maven - Users mailing list archive at Nabble.com. - 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]
