You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Felix Knecht <fe...@otego.com> on 2008/06/11 14:40:19 UTC
Continuum deployment of studio
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Pierre-Arnaud
In the sutdio/turnk/pom.xml we do have a studio artifact having a non snapshot version (see diff below). This makes it
for continuum impossible to deploy the artifact, because of suffering karma.
Snapshot artifact version are deployed to vm094.oxylos.org - what works well - whereas non snapshot artifacts are tried
to be deployed somewhere at apache.org - where continuum doesn't has access.
Can we change the apacheds.launcher.version to snapshot like all the others are?
Regards
Felix
felix@pcfelix ~/svn/apache/directory/studio/trunk $ svn diff pom.xml
Index: pom.xml
===================================================================
- --- pom.xml (revision 666641)
+++ pom.xml (working copy)
@@ -62,7 +62,7 @@
~ <properties>
~ <!-- Set versions for subprojects -->
~ <aciitemeditor.version>1.2.0.SNAPSHOT</aciitemeditor.version>
- - <apacheds.launcher.version>1.2.0</apacheds.launcher.version>
+ <apacheds.launcher.version>1.2.0.SNAPSHOT</apacheds.launcher.version>
~ <apacheds.version>1.2.0.SNAPSHOT</apacheds.version>
~ <apacheds.help.version>1.2.0.SNAPSHOT</apacheds.help.version>
~ <apacheds.feature.version>1.2.0.SNAPSHOT</apacheds.feature.version>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkhPx7MACgkQ2lZVCB08qHFVMgCg8NRWznBI3JAbYPCRJNV24Qic
BywAoLsMwEKzA7l7oABd9SJIU1T9dBLk
=FMRE
-----END PGP SIGNATURE-----
Re: Continuum deployment of studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On Wed, Jun 11, 2008 at 3:05 PM, Felix Knecht <fe...@apache.org> wrote:
> Pierre-Arnaud Marcelot schrieb:
>
>> Hi Felix,
>>
>> Actually, it would be better if we don't change the version number on
>>
> this project.
>
>> It is used and bundled in the Apache DS plugin, and the version is
>>
> hardcoded in the coded of the plugin (sorry but it was needed and I had no
> other solution)...
>
> Can't we use filtering here?
I dont know... Let me explain the situation.
To launch Apache DS within Studio, I need to put all the Apache DS jars in a
special folder (handled by the plugin). So before launching a new instance
of Apache DS, I verify that this folder contains the needed dependencies, if
not I copy them (they are in the plugin's jar).
Once that verification is done, I need to prepare the classpath of a new
"launch configuration" (some kind of JVM configuration for launching Java
application from within Eclipse) by providing the paths to these jars.
Right now, the names of the jars are contained in a public static final
array of Strings. Is this filterable ?
> I don't know. Regarding [2] there's no other way :(. If it's a problem of
> compilation you can try to increase mem for this task [3], but I'm not sure
> if it helps.
>
> [1] http://maven.apache.org/plugins/maven-deploy-plugin/usage.html
> [2]
> http://www.nabble.com/MAVEN_OPTS-in-pom.xml-or-settings.xml--td15081454s177.html
> [3]
> http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-with-memory-enhancements.html
>
Yeah, that's what I saw for the [2]... :(
Unfortunately, the problem does not occur when compiling java code, but
docbook code.
I believe the docbook generation done using an ant task is using too much
memory and I think we can't specify the memory used by the maven-ant plugin
(I have to take a closer look).
Regards,
Pierre-Arnaud
Re: Continuum deployment of studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Hi Felix,
>
> Actually, it would be better if we don't change the version number on
this project.
> It is used and bundled in the Apache DS plugin, and the version is
hardcoded in the coded of the plugin (sorry but it was needed and I had
no other solution)...
Can't we use filtering here?
>
> Is there another way than going to SNAPSHOT ?
We can try to overwrite [1] the distribution repository for non
snapshots (only for this artifact). But we'll need to remember to reset
this when doing a real deployment (i.e. for when releasing). Otherwise
it'll get deployed to a wrong location.
>
> BTW, Felix, I have another Maven question. I added the new Apache DS
feature to the build and it includes 4 new projects. When I try to build
it using "mvn clean install", I got an error telling me I don't have
enough memory. I need to use this command "MAVEN_OPTS="-Xmx256m" mvn
clean install" to build the projects correctly.
> Is there any way this could be corrected (or added the build) ?
I don't know. Regarding [2] there's no other way :(. If it's a problem
of compilation you can try to increase mem for this task [3], but I'm
not sure if it helps.
[1] http://maven.apache.org/plugins/maven-deploy-plugin/usage.html
[2]
http://www.nabble.com/MAVEN_OPTS-in-pom.xml-or-settings.xml--td15081454s177.html
[3]
http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-with-memory-enhancements.html
Felix
>
> Thanks,
> Pierre-Arnaud
>
>
> On Wed, Jun 11, 2008 at 2:40 PM, Felix Knecht <felix@otego.com
<ma...@otego.com>> wrote:
>
> Hi Pierre-Arnaud
>
>
> In the sutdio/turnk/pom.xml we do have a studio artifact having a non
> snapshot version (see diff below). This makes it
> for continuum impossible to deploy the artifact, because of suffering
> karma.
> Snapshot artifact version are deployed to vm094.oxylos.org
> <http://vm094.oxylos.org> - what works well - whereas non snapshot
> artifacts are tried
> to be deployed somewhere at apache.org <http://apache.org> - where
> continuum doesn't has access.
>
> Can we change the apacheds.launcher.version to snapshot like all the
> others are?
>
> Regards
> Felix
>
>
> felix@pcfelix ~/svn/apache/directory/studio/trunk $ svn diff pom.xml
> Index: pom.xml
> ===================================================================
> --- pom.xml (revision 666641)
> +++ pom.xml (working copy)
> @@ -62,7 +62,7 @@
> ~ <properties>
> ~ <!-- Set versions for subprojects -->
> ~ <aciitemeditor.version>1.2.0.SNAPSHOT</aciitemeditor.version>
> - <apacheds.launcher.version>1.2.0</apacheds.launcher.version>
> + <apacheds.launcher.version>1.2.0.SNAPSHOT</apacheds.launcher.version>
> ~ <apacheds.version>1.2.0.SNAPSHOT</apacheds.version>
> ~ <apacheds.help.version>1.2.0.SNAPSHOT</apacheds.help.version>
> ~ <apacheds.feature.version>1.2.0.SNAPSHOT</apacheds.feature.version>
Re: Hardcoded Version
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> This could be a solution, but I think this will be a problem when we
> try the plugins (Run and Debug) within Eclipse, as the placeholder
> will not be replaced by its value...
>
> WDYT ?
I've absolutely no idea if it works or not :-)
If I find some time I'll give it a try later.
>
> Pierre-Arnaud
>
> On Wed, Jun 11, 2008 at 3:19 PM, Felix Knecht <felixk@apache.org
> <ma...@apache.org>> wrote:
>
> Felix Knecht schrieb:
>
> Pierre-Arnaud Marcelot schrieb:
>
> Hi Felix,
>
> Actually, it would be better if we don't change the
> version number on
>
> this project.
>
> It is used and bundled in the Apache DS plugin, and the
> version is
>
> hardcoded in the coded of the plugin (sorry but it was needed
> and I had no other solution)...
>
> Is it in the apacheds/.../ApacheDsPluginUtils.java?
>
> What about reading this things
> - String APACHEDS_VERSION = "1.5.2"
> - String[] apachedsLibraries
> from a properties file located somewhere in the resource
> folder and having the resource file filtered with the wanted
> version?
>
>
> It's not even needed to have a properties file, it can even be
> done in the java source file, see
> http://www.gxdeveloperweb.com/Blogs/Bram-de-Kruijff/Maven-secrets-filtering-sources.htm
>
>
> Felix
>
>
>
Re: Hardcoded Version
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
This could be a solution, but I think this will be a problem when we try the
plugins (Run and Debug) within Eclipse, as the placeholder will not be
replaced by its value...
WDYT ?
Pierre-Arnaud
On Wed, Jun 11, 2008 at 3:19 PM, Felix Knecht <fe...@apache.org> wrote:
> Felix Knecht schrieb:
>
>> Pierre-Arnaud Marcelot schrieb:
>>
>>> Hi Felix,
>>>
>>> Actually, it would be better if we don't change the version number on
>>>
>> this project.
>>
>>> It is used and bundled in the Apache DS plugin, and the version is
>>>
>> hardcoded in the coded of the plugin (sorry but it was needed and I had no
>> other solution)...
>>
>> Is it in the apacheds/.../ApacheDsPluginUtils.java?
>>
>> What about reading this things
>> - String APACHEDS_VERSION = "1.5.2"
>> - String[] apachedsLibraries
>> from a properties file located somewhere in the resource folder and having
>> the resource file filtered with the wanted version?
>>
>
> It's not even needed to have a properties file, it can even be done in the
> java source file, see
>
> http://www.gxdeveloperweb.com/Blogs/Bram-de-Kruijff/Maven-secrets-filtering-sources.htm
>
>>
>> Felix
>>
>>
>
Re: Hardcoded Version
Posted by Felix Knecht <fe...@apache.org>.
Felix Knecht schrieb:
> Pierre-Arnaud Marcelot schrieb:
>> Hi Felix,
>>
>> Actually, it would be better if we don't change the version number on
> this project.
>> It is used and bundled in the Apache DS plugin, and the version is
> hardcoded in the coded of the plugin (sorry but it was needed and I
> had no other solution)...
>
> Is it in the apacheds/.../ApacheDsPluginUtils.java?
>
> What about reading this things
> - String APACHEDS_VERSION = "1.5.2"
> - String[] apachedsLibraries
> from a properties file located somewhere in the resource folder and
> having the resource file filtered with the wanted version?
It's not even needed to have a properties file, it can even be done in
the java source file, see
http://www.gxdeveloperweb.com/Blogs/Bram-de-Kruijff/Maven-secrets-filtering-sources.htm
>
> Felix
>
Re: Hardcoded Version (was Continuum deployment of studio)
Posted by Alex Karasulu <ak...@apache.org>.
FYI, this is what we do for ADS.
Alex
On Wed, Jun 11, 2008 at 9:14 AM, Felix Knecht <fe...@apache.org> wrote:
> Pierre-Arnaud Marcelot schrieb:
>
>> Hi Felix,
>>
>> Actually, it would be better if we don't change the version number on
>>
> this project.
>
>> It is used and bundled in the Apache DS plugin, and the version is
>>
> hardcoded in the coded of the plugin (sorry but it was needed and I had no
> other solution)...
>
> Is it in the apacheds/.../ApacheDsPluginUtils.java?
>
> What about reading this things
> - String APACHEDS_VERSION = "1.5.2"
> - String[] apachedsLibraries
> from a properties file located somewhere in the resource folder and having
> the resource file filtered with the wanted version?
>
> Felix
>
>
Hardcoded Version (was Continuum deployment of studio)
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Hi Felix,
>
> Actually, it would be better if we don't change the version number on
this project.
> It is used and bundled in the Apache DS plugin, and the version is
hardcoded in the coded of the plugin (sorry but it was needed and I had
no other solution)...
Is it in the apacheds/.../ApacheDsPluginUtils.java?
What about reading this things
- String APACHEDS_VERSION = "1.5.2"
- String[] apachedsLibraries
from a properties file located somewhere in the resource folder and
having the resource file filtered with the wanted version?
Felix
Re: Continuum deployment of studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Felix,
Actually, it would be better if we don't change the version number on this
project.
It is used and bundled in the Apache DS plugin, and the version is hardcoded
in the coded of the plugin (sorry but it was needed and I had no other
solution)...
Is there another way than going to SNAPSHOT ?
BTW, Felix, I have another Maven question. I added the new Apache DS feature
to the build and it includes 4 new projects. When I try to build it using
"mvn clean install", I got an error telling me I don't have enough memory. I
need to use this command "MAVEN_OPTS="-Xmx256m" mvn clean install" to build
the projects correctly.
Is there any way this could be corrected (or added the build) ?
Thanks,
Pierre-Arnaud
On Wed, Jun 11, 2008 at 2:40 PM, Felix Knecht <fe...@otego.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Pierre-Arnaud
>
>
> In the sutdio/turnk/pom.xml we do have a studio artifact having a non
> snapshot version (see diff below). This makes it
> for continuum impossible to deploy the artifact, because of suffering
> karma.
> Snapshot artifact version are deployed to vm094.oxylos.org - what works
> well - whereas non snapshot artifacts are tried
> to be deployed somewhere at apache.org - where continuum doesn't has
> access.
>
> Can we change the apacheds.launcher.version to snapshot like all the others
> are?
>
> Regards
> Felix
>
>
> felix@pcfelix ~/svn/apache/directory/studio/trunk $ svn diff pom.xml
> Index: pom.xml
> ===================================================================
> - --- pom.xml (revision 666641)
> +++ pom.xml (working copy)
> @@ -62,7 +62,7 @@
> ~ <properties>
> ~ <!-- Set versions for subprojects -->
> ~ <aciitemeditor.version>1.2.0.SNAPSHOT</aciitemeditor.version>
> - - <apacheds.launcher.version>1.2.0</apacheds.launcher.version>
> + <apacheds.launcher.version>1.2.0.SNAPSHOT</apacheds.launcher.version>
> ~ <apacheds.version>1.2.0.SNAPSHOT</apacheds.version>
> ~ <apacheds.help.version>1.2.0.SNAPSHOT</apacheds.help.version>
> ~ <apacheds.feature.version>1.2.0.SNAPSHOT</apacheds.feature.version>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkhPx7MACgkQ2lZVCB08qHFVMgCg8NRWznBI3JAbYPCRJNV24Qic
> BywAoLsMwEKzA7l7oABd9SJIU1T9dBLk
> =FMRE
> -----END PGP SIGNATURE-----
>