it would be better to use a profile instead of to use all properties on the
command line.
Emmanuel
Morgovsky, Alexander (US - Glen Mills) a écrit :
It is more than 300 characters of custom properties with their values set using
-D parameters. However, I decided to use less characters, thus I am fine for
now. Thank you.
-----Original Message-----
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, November 26, 2007 7:30 AM
To: continuum-users@maven.apache.org
Subject: Re: Build definitions which exceed the default length
Can we know values you use in this screen?
Emmanuel
Morgovsky, Alexander (US - Glen Mills) a écrit :
Sure.
On the Add/Edit Build Definition page, after entering the definition, I
receive this error:
org.apache.maven.continuum.ContinuumException: Error while executing the
action 'update-build-definition-from-project-group'
The Stack Trace contains:
Caused by: javax.jdo.JDOFatalUserException: Attempt to store value "<my
definition>" in column "ARGUMENTS" that has maximum length of 256.
Please correct your data!
at
org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping
.java:214)
at
org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.j
ava:203)
at
org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(Param
eterSetter.java:122)
at
org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.jav
a:2757)
at
org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField
(BuildDefinition.java)
at
org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField
s(BuildDefinition.java)
at
org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115
)
at
org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:25
9)
at
org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2573)
at org.jpox.store.StoreManager.update(StoreManager.java:967)
at
org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4928)
at
org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav
a:3217)
at
org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMSNonmanagedTr
ansaction.java:397)
at
org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject(PlexusJdoUtils.java:
163)
at
org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti
nuumStore.java:794)
at
org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti
nuumStore.java:786)
at
org.apache.maven.continuum.store.JdoContinuumStore.storeBuildDefinition(
JdoContinuumStore.java:707)
at
org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumA
ction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction
.java:181)
at
org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectG
roupAction.execute(UpdateBuildDefinitionFromProjectGroupAction.java:51)
at
org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinu
um.java:2432)
... 81 more
-----Original Message-----
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 24, 2007 9:34 PM
To: continuum-users@maven.apache.org
Subject: Re: Build definitions which exceed the default length
On Nov 24, 2007 7:23 PM, Morgovsky, Alexander (US - Glen Mills)
<[EMAIL PROTECTED]> wrote:
Continuum does not allow build definitions to be longer than a
specified
length. What is the suggested work-around for this issue? Thank you.
There are several fields on the add/edit build definition page. Is
one of the fields too short, or is it accepting your input and then
complaining later?
Please explain the steps needed to reproduce the problem.
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message.
Any disclosure, copying, or distribution of this message, or the taking of any
action based on it, is strictly prohibited. [v.E.1]
