Thanks Dan,
>test
I've raised JIRA ticket re the failed test.
>mvn jetty:run
Confirmed, I'm not using -o
Confirmed, there are no messages saying it can't find
org.codehaus.mojo:maven-jetty-plugin
I've checked in my /usr/share/java/maven-2.2.1/conf/settings.xml and it looks
as you say.
I've tried deleting the jetty plugins from my .m2, even deleting the whole of
org/mortbay/jetty, same bad.
My error definitely refers to org.apache.maven.plugins, though the stacktrace
refers to Mojo, see below, could there be some other config that's affecting
this?
I even tried to force it by adding
<pluginGroup>org.codehaus.mojo</pluginGroup> to settings.xml
> [groupId].[artifactId];
Yes I specified this, both with and without the semicolon.
Best regards
Mike Burton
Stacktrace from mvn -e jetty:run ...
[INFO] The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist
or no valid version could be found
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid
version could be found
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:462)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:175)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The
plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid
version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:229)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:91)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:179)
at
org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540)
... 15 more
On 3 Dec 2010, at 10:51, Dan Haywood wrote:
> Hi Mike,
>
> On 02/12/2010 20:08, Mike Burton wrote:
>> Now I'm trying to run the webapp-based Scimpi viewer...
>>
>> mvn jetty:run gives error:
>> The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist...
>
> Strange.
>
> First things first... I presume you're not using -o (-offline)?
>
> But secondly, the plugin isn't at org.apache, it's at codehaus [1] If you go
> to $MAVEN_HOME/conf/settings.xml, you'll see that the <pluginGroups> comments
> explain that Maven searches for both org.apache.maven.plugins and
> org.codehaus.mojo. Is there more to the message saying it can't find
> org.codehaus.mojo:maven-jetty-plugin also?
>
>
> [1] http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin
>
>
>> I tried deploying Scimpi.war into my existing Tomcat6 but it clashes with
>> commons-logging.jar, then servlet-api (the app has its own copy in its
>> lib/), then I get a StartupServletContextListener NoClassDef (MyFaces
>> clash??)
> Hmm, not sure. Rob, have you tried running scimpi.war this way?
>
>
>> I also tried running the .launch and got:
>> Launch configuration prototype-viewer-bdd references non-existing project
>> org.apache.isis.support.prototype-viewer-bdd
>> but this project does seem to exist.
> When you import using m2eclipse, make sure that you go to Advanced>Name
> Templates and specified [groupId].[artifactId]; this is referenced in the
> .launch file.
>
>
>> Tried a build/ clean in Eclipse and got several errors like:
>> org.eclipse.debug.core.DebugException: org.xml.sax.SAXParseException:
>> Content is not allowed in prolog. occurred while reading launch
>> configuration file:
>> /Users/mikeburton/DEV/ISIS/projs/isis01/support/archetypes/exploration/target/classes/archetype-resources/ide/eclipse/launch/Isis
>> (DnD).launch.
>> at org.eclipse.debug.internal.core.LaunchManager.createDebugException
>> I guess I need to process the 3 #set( lines at the top of the .launch
>> file somehow?
> That error probably is the script that Rob ran against all XML files that's
> put the ASF copyright notice in the wrong place (must be after the prolog,
> not before).
>
> But in any case, the plan is to recreate the archetypes by reverse
> engineering from support/prototype once .
>
> So, you can ignore that as non-fatal.
>
>
>> My preference would be to get mvn jetty:run to work but the Eclipse stuff
>> would be "nice to have"
>>
>> Any ideas please?
>>
> Hopefully some of the above?
>
>
>> Best Regards
>>
>> Mike Burton
>>
>> On 2 Dec 2010, at 18:15, Mike Burton wrote:
>>
>>> Hi Dan,
>>>
>>> Re my earlier error with servlet-api-2.5.jar I tried your suggestion,
>>> I deleted the ~/.m2/.../2.5 folder so that Maven would re-fetch it, but got
>>> the same error.
>>> Looking back through the build output for when it downloaded
>>> servlet-api-2.5.jar (from
>>> https://maven-repository.dev.java.net/nonav/repository/javax.servlet/jars/
>>> ) it got a "checksum failed" error.
>>>
>>> So I downloaded servlet-api-2.5.jar also .pom and also the .sha1 files for
>>> them both, from
>>> http://repository.jboss.org/maven2/javax/servlet/servlet-api/2.5/ instead,
>>> into my Maven repository.
>>>
>>> Now mvn clean install -D modules=all -o works. I just get one test
>>> failure:
>>> /tmp/concordion/org/apache/isis/support/prototype/stories/NewClaimDefaultsOkStory.html
>>> Successes: 17, Failures: 1
>>>
>>>
>>> Best Regards
>>>
>>> Mike Burton
>>>
>>>
>>>
>>>
>>> On 19 Nov 2010, at 11:07, Dan Haywood wrote:
>>>
>>>> Hi Mike,
>>>> thx for taking the time... within
>>>>
>>>> On 19/11/2010 10:28, Mike Burton wrote:
>>>>> Hi Folks,
>>>>>
>>>>> Just built on my Mac, using Maven 2.2.1 and JDK 1.6.0_22
>>>> +1.
>>>>
>>>> BTW, I think the standard build ("clean install") should work on Maven 3.0
>>>> (Vango reported as such), but my understanding is that mvn 3.0 has
>>>> rejigged the way that the site plugin works, so "site-deploy" won't.
>>>> There's a JIRA ticket for this [3] ... until we tackle it, I think we
>>>> should say that Maven 2.2.1 is the only version of Maven we're supporting.
>>>>
>>>>> Apologies if some of these have already been reported...
>>>>>
>>>>> 1. mvn clean install succeeds, but some test failures in
>>>>> alternatives/objectstore/nosql/target/surefire-reports:
>>>>> org.apache.isis.alternatives.objectstore.nosql.DestroyObjectCommandImplementationTest.txt
>>>>> org.apache.isis.alternatives.objectstore.nosql.NoSqlObjectStoreTest.txt
>>>>> org.apache.isis.alternatives.objectstore.nosql.ObjectReaderTest.txt
>>>>> org.apache.isis.alternatives.objectstore.nosql.SerialKeyCreatorTest.txt
>>>>> org.apache.isis.alternatives.objectstore.nosql.SystemTest.txt
>>>>> org.apache.isis.alternatives.objectstore.nosql.WriteObjectCommandTest.txt
>>>> Not sure, "works for me".
>>>>
>>>> Rob, any clues?
>>>>
>>>>
>>>>> 2. mvn clean install -D modules=all
>>>>> [ERROR] error: error reading
>>>>> /Users/mikeburton/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar;
>>>>> cannot read zip file
>>>> This looks like a corruption in your local Maven repo. Just delete that
>>>> JAR (or even the "2.5" directory) to force Maven to download again.
>>>>
>>>> Once you do get a clean build, I recommend "-o" to speed up subsequent
>>>> builds.
>>>>
>>>>
>>>>> 3. mvn site-deploy -D modules=standard -D site=full -D deploy=local
>>>>> [INFO] Velocimacro : adding VMs from VM library template :
>>>>> VM_global_library.vm
>>>>> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm'
>>>>> in any resource loader.
>>>>> ...
>>>>> .. Cobertura... [INFO] There are 3 checkstyle errors.
>>>>> ...
>>>> Don't worry about checkstyle stuff just yet... we'll tackle that later on.
>>>>
>>>>
>>>>
>>>>> Missing: com.java:jimi:jar:1.0
>>>>> for artifact:
>>>>> com.agilejava.docbkx:docbkx-maven-plugin:maven-plugin:2.0.8
>>>>>
>>>> It's necessary to install the JIMI jar first. There is a note in the
>>>> trunk/pom.xml, but I've also just updated the BuildProcess page on the
>>>> wiki [1] to document this as a prereq
>>>>
>>>>
>>>>
>>>>
>>>>> 4. For completeness we need to add this to beginning of build
>>>>> instructions:
>>>>>
>>>>> Make a directory and download the software into it:
>>>>> svn co http://svn.apache.org/repos/asf/incubator/isis/trunk .
>>>>>
>>>> Done, in [2]
>>>>
>>>>> Allocate sufficient memory for the JVM, to avoid heap space error in
>>>>> Maven:
>>>>> export MAVEN_OPTS=-Xmx512m
>>>>> //TODO or the Windows equivalent
>>>>>
>>>> This is documented already, in [2]
>>>>
>>>>> Maybe add svn to list of prerequisites? or is that too obvious?
>>>> Done, in [2]
>>>>
>>>>
>>>>> Mike
>>>> Mike ... if you haven't already, register on the wiki and send a mail here
>>>> to isis-dev to get write permissions. Mark is the man with the karma to
>>>> hand out the karma. Then you can make any updates directly yourself ;-)
>>>>
>>>>
>>>> [1] https://cwiki.apache.org/confluence/display/ISIS/BuildProcess
>>>> [2]
>>>> https://cwiki.apache.org/confluence/display/ISIS/SettingUpDevelopmentEnvironment
>>>> [3] https://issues.apache.org/jira/browse/ISIS-11
>>>>
>>
