[jira] Created: (MNG-3881) Properties in plugin poms are not resolved.
Properties in plugin poms are not resolved.
---
Key: MNG-3881
URL: http://jira.codehaus.org/browse/MNG-3881
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.1.0-M1
Environment: Mac ox s
Reporter: Derek Clarkson
I'm testing a plugin I have written to run JUnit 4.x tests. The pom for this
plug uses properties to specify the versions of dependencies. ie.
junit
junit
${junit.version}
org.slf4j
slf4j-api
${slf4j.version}
After compiling and installing the plugin into my local repository, I then
attempt to use in in another project. The project compiles correcly, but then
fails when attempting to resolve the dependecies of my plugin. The faiures
appear to be the plugins dependencies which are versioned by properties. HEre's
an example:
6) org.slf4j:slf4j-api:jar:${slf4j.version}
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.slf4j -DartifactId=slf4j-api
-Dversion=${slf4j.version} -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.slf4j -DartifactId=slf4j-api
-Dversion=${slf4j.version} -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
Path to dependency:
1) dhc.maven2:maven-junit4x-plugin:maven-plugin:0.0.3-SNAPSHOT
2) org.slf4j:slf4j-api:jar:${slf4j.version}
I also see stack traces like this:
Caused by: java.io.FileNotFoundException:
http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/${maven.reporting.version}/maven-reporting-impl-${maven.reporting.version}.jar
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1239)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:83)
... 35 more
[DEBUG] Unable to download the artifact from any repository
And
7 required artifacts are missing.
for artifact:
dhc.maven2:maven-junit4x-plugin:maven-plugin:0.0.3-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:482)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:394)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:337)
at
org.apache.maven.plugin.DefaultPluginManager.getPluginArtifacts(DefaultPluginManager.java:436)
at
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:279)
at
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:211)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:186)
at
org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPluginLoader.java:79)
... 20 more
Plaing around with this I found that if I go into the repository and edit the
pom file to specify the dependency version then that dependency resolves.
>From this I'm inclined to think that when resolving dependencies of plugins,
>that the plugin's pom is not being processed to look for properties to be
>inserted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1241) Schedule fails to start due to derby database column being too small
[ http://jira.codehaus.org/browse/CONTINUUM-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97438 ] Derek Clarkson commented on CONTINUUM-1241: --- Actually never heard of JPOX before this and wasn't aware it produced any log. We basically established through experimentation that it's the length of a svn log line that causes the issue. Keeping them under 255 seems to avoid the bug. > Schedule fails to start due to derby database column being too small > > > Key: CONTINUUM-1241 > URL: http://jira.codehaus.org/browse/CONTINUUM-1241 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.0.3 > Environment: Linux >Reporter: Derek Clarkson >Priority: Critical > > When the schedular trys to start a build we get the following error: > INFO | jvm 1| 2007/04/10 10:30:08 | ERROR 22001: A truncation error was > encountered trying to shrink VARCHAR > '/Magrathea/trunk/bizstation-magrathea/customer-core/src/main&' to length 255. > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.error.StandardException.newException(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknown > Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unknown > Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unknown > Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown > Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.request.Request.executeUpdate(Request.java:78) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:258) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.StoreManager.insert(StoreManager.java:739) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3415) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3388) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1146) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1187) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.scostore.InverseListStore.validateElementForWriting(InverseListStore.java:1061) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.scostore.InverseListStore.internalAdd(InverseListStore.java:672) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.scostore.AbstractListStore.addAll(AbstractListStore.java:322) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.mapping.CollectionMapping.postInsert(CollectionMapping.java:236) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:396) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.StoreManager.insert(StoreManager.java:739) > INFO | jvm 1| 2007/04/10 10:30:08 | at
[jira] Created: (CONTINUUM-1241) Schedule fails to start due to derby database column being too small
Schedule fails to start due to derby database column being too small Key: CONTINUUM-1241 URL: http://jira.codehaus.org/browse/CONTINUUM-1241 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.0.3 Environment: Linux Reporter: Derek Clarkson Priority: Critical When the schedular trys to start a build we get the following error: INFO | jvm 1| 2007/04/10 10:30:08 | ERROR 22001: A truncation error was encountered trying to shrink VARCHAR '/Magrathea/trunk/bizstation-magrathea/customer-core/src/main&' to length 255. INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.rdbms.request.Request.executeUpdate(Request.java:78) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:258) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.StoreManager.insert(StoreManager.java:739) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3415) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3388) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1146) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1187) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.rdbms.scostore.InverseListStore.validateElementForWriting(InverseListStore.java:1061) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.rdbms.scostore.InverseListStore.internalAdd(InverseListStore.java:672) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.rdbms.scostore.AbstractListStore.addAll(AbstractListStore.java:322) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.mapping.CollectionMapping.postInsert(CollectionMapping.java:236) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:396) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.StoreManager.insert(StoreManager.java:739) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3415) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3388) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1146) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1187) INFO | jvm 1| 2007/04/10 10:30:08 | at org.jpox.store.rdbms.scostore.InverseListStore.validat
[jira] Created: (WAGON-74) WebDav component references non-existant jetty pom and fails to install into maven when building.
WebDav component references non-existant jetty pom and fails to install into maven when building. - Key: WAGON-74 URL: http://jira.codehaus.org/browse/WAGON-74 Project: wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-2 Environment: Maven 2.0.5 Reporter: Derek Clarkson Priority: Blocker When attempt to deploy using the webdav to a local Archiva repository I get the message: Protocol [dav] is unsupported by the current configuration. Turning on debug I see at the top of the log: [DEBUG] Artifact not found - using stub model: Unable to download the artifact from any repository org.mortbay.jetty:jetty:pom:4.2.12 from the specified remote repositories: central (http://repo1.maven.org/maven2), aegeon-proxy (http://192.168.0.91:/proxy/aegeon) Looking inside the repo1.maven.org/maven2 repository I can see that the directory exists for jetty 4.2.12 but there is no pom in it. My build pom makes reference to the following extension: org.apache.maven.wagon wagon-webdav 1.0-beta-2 Please suggest a fix as this is blocking our development because we cannot deploy to our local Archiva server. ciao Derek -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
