-
10:31:54 AM mlei: i'm taking a look at an issue where there's a singleton constraint but it's still letting me load-objects 2 of the same one
10:45:51 AM mlei: i.e. AtgJBossServer constrains to singleton AtgJBossTransactionTimeout
10:46:02 AM mlei: but load-objects let me add a new one, even though there was already one there
1:37:51 PM Greg Schueler: mlei: yeah reproduced the singleton issue.
2009-12-21 23:47:45 UTC in ControlTier
-
moseslei committed revision 1840 to the ModuleForge SVN repository, changing 4 files.
2009-12-18 19:10:22 UTC in ModuleForge
-
moseslei committed revision 1837 to the ModuleForge SVN repository, changing 1 files.
2009-12-17 22:19:05 UTC in ModuleForge
-
brahms:~/src/3-4-support/core/modules mlei$ svn ci -m 'Allow BuilderBuildstamp to be a child of Site, bug 2915291'
Sending modules/Builder/type.xml
Sending modules/Site/type.xml
Transmitting file data ..
Committed revision 1834.
2009-12-16 04:44:20 UTC in ControlTier
-
moseslei committed revision 1834 to the ModuleForge SVN repository, changing 2 files.
2009-12-16 04:42:58 UTC in ModuleForge
-
Site should allow a singleton BuilderBuildstamp object so that Site can benefit from default buildstamp support.
2009-12-16 04:42:27 UTC in ControlTier
-
[deploy@jdev-ctier Builder]$ svn ci -m 'Add support in Builder#repoImport for build artifacts named myproject-1.0.war (bug 2915278)'
Sending Builder/commands/repoFindAndPurge.xml
Sending Builder/commands/repoImport.xml
Sending Builder/commands/repoPurge.xml
Sending Builder/commands/scmCheckout.xml
Sending Builder/type.xml
Transmitting file data .......
2009-12-16 04:26:06 UTC in ControlTier
-
moseslei committed revision 1833 to the ModuleForge SVN repository, changing 5 files.
2009-12-16 04:24:38 UTC in ModuleForge
-
repoImport currently only supports artifacts named project.ext or project-buildstamp.ext. It should also support artifacts named project-versionmajor.versionminor.versionrelease.ext, such as:
myproject-1.0.war
This is a very common name for a build artifact in Maven and grails builds.
2009-12-16 04:23:53 UTC in ControlTier
-
The install.sh script does not check if $JAVA_HOME/lib/tools.jar is available. This leads to a successful install but a non-working Workbench (fails on jsp compilation).
On a server install, we should check if it's there and fail if it is not.
2009-12-15 19:12:59 UTC in ControlTier
