You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Stefan Zoerner <SZ...@de.ibm.com> on 2006/01/30 11:26:47 UTC
Failed to build the uberjar of ApacheDS
Hi all,
I tried to build the uberjar (standalone executyble ApacheDS in a jar) from
directory trunks/apacheds via mvn -e assemby:assembly but it fails with
message
[INFO] [assembly:assembly]
[INFO]
-------------------------------------------------------------------------
---
[ERROR] BUILD FAILURE
[INFO]
-------------------------------------------------------------------------
---
[INFO] No assembly descriptors found.
[INFO]
-------------------------------------------------------------------------
---
[INFO] Trace
org.apache.maven.BuildFailureException: No assembly descriptors found. ...
A mvn install runs succesful. I probably make/understand something wrong
(but what) ...
Any help is welcome,
Stefan
I probably have to improve my m2 skills, anyhow :-(
Re: Failed to build the uberjar of ApacheDS
Posted by Alex Karasulu <ao...@bellsouth.net>.
Stefan Zoerner wrote:
>Hi all,
>
>I tried to build the uberjar (standalone executyble ApacheDS in a jar) from
>directory trunks/apacheds via mvn -e assemby:assembly but it fails with
>message
>
>[INFO] [assembly:assembly]
>[INFO]
>-------------------------------------------------------------------------
>---
>[ERROR] BUILD FAILURE
>[INFO]
>-------------------------------------------------------------------------
>---
>[INFO] No assembly descriptors found.
>[INFO]
>-------------------------------------------------------------------------
>---
>[INFO] Trace
>org.apache.maven.BuildFailureException: No assembly descriptors found. ...
>
>A mvn install runs succesful. I probably make/understand something wrong
>(but what) ...
>Any help is welcome,
> Stefan
>
>I probably have to improve my m2 skills, anyhow :-(
>
>
>
No no uberjar is in a messed up state probably. Switching to using
installers. We probably spoke about this already on IRC. If you have
any questions feel free to ping me.
Laters,
Alex
Re: Failed to build the uberjar of ApacheDS
Posted by Alex Karasulu <ao...@bellsouth.net>.
Stefan Zoerner wrote:
> Alex Karasulu wrote:
>
>>
>> Exactly that's correct. You still need this uberjar to work? It may
>> have issues now that we are using this new directory layout for the
>> server. I can however create this layout on startup if a path to it
>> is not specified on the command line. The intersting thing is how to
>> handle this since the uberjar has everything on in the System
>> ClassLoader. I have to play with it some more but I can make the
>> uberjar work again if it does not already. It just seemed as though
>> many did not like it.
>>
>> Alex
>>
>>
>>
> Alex,
>
> sorry, I have forgotten to answer you regarding the uberjar.
>
> I liked the uberjar because it was easy to switch the build/version by
> just replacing one single file. So it was easy to reproduce error
> reports in JIRA and from the mailing list with the exact version the
> user used (and check how "old" the defect is).
>
> You did a great job with the installers, and probably our upcoming
> users (especially newbies) will not use the uberjar anymore (but the
> official installer downloads) if we have a stable "setup.exe" for most
> platforms.
>
> Therefore I can live without (i.e. do not any extra work to make it
> work just for me!), but if any other reasons speak for the uberjar as
> well, I will be happy to keep my lazy style of switching between build
> versions ...
Stephan I fixed the uberjar and also added a few things to it. Please
make sure it works to your liking. Also you can kickstart the build of
the assembly by just trying to start the server with an apacheds.sh
script that I put the top directory. Now your life gets really easy.
Now I expect some juicy detailed bug reports :).
Alex
Re: Failed to build the uberjar of ApacheDS
Posted by Stefan Zoerner <sz...@apache.org>.
Alex Karasulu wrote:
>
> Exactly that's correct. You still need this uberjar to work? It may
> have issues now that we are using this new directory layout for the
> server. I can however create this layout on startup if a path to it is
> not specified on the command line. The intersting thing is how to
> handle this since the uberjar has everything on in the System
> ClassLoader. I have to play with it some more but I can make the
> uberjar work again if it does not already. It just seemed as though
> many did not like it.
>
> Alex
>
>
>
Alex,
sorry, I have forgotten to answer you regarding the uberjar.
I liked the uberjar because it was easy to switch the build/version by
just replacing one single file. So it was easy to reproduce error
reports in JIRA and from the mailing list with the exact version the
user used (and check how "old" the defect is).
You did a great job with the installers, and probably our upcoming users
(especially newbies) will not use the uberjar anymore (but the official
installer downloads) if we have a stable "setup.exe" for most platforms.
Therefore I can live without (i.e. do not any extra work to make it work
just for me!), but if any other reasons speak for the uberjar as well, I
will be happy to keep my lazy style of switching between build versions ...
Greetings, Stefan
Re: Failed to build the uberjar of ApacheDS
Posted by Alex Karasulu <ao...@bellsouth.net>.
Stefan Zoerner wrote:
> Alan D. Cabrera wrote:
>
>> On 1/30/2006 2:26 AM, Stefan Zoerner wrote:
>>
>>> Hi all,
>>>
>>> I tried to build the uberjar (standalone executyble ApacheDS in a
>>> jar) from
>>> directory trunks/apacheds via mvn -e assemby:assembly but it fails with
>>> message ...
>>>
>>
>> We have this same problem in Geronimo. I think that it's a known
>> bug. You have to run that command in the actual assembly directory.
>> Another thing, we get a -null.jar at the end of the jar name. Please
>> confirm if this is the case for you as well.
>>
>
> Thanks Alan,
>
> I was finally able to build it from directory
> .../trunks/apacheds/standalone/simple/main
> with command
> mvn assembly:assembly
>
> But the result has no -null.jar at the end, it is called
> org.apache.ldap.server.standalone.simple.main-0.9.4-SNAPSHOT-app.jar
>
> I confess: I do not understand much from m2 configuration, but I
> assume this "app" comes from the classifier config in the pom.xml in
> the directory mentioned above :
Exactly that's correct. You still need this uberjar to work? It may
have issues now that we are using this new directory layout for the
server. I can however create this layout on startup if a path to it is
not specified on the command line. The intersting thing is how to
handle this since the uberjar has everything on in the System
ClassLoader. I have to play with it some more but I can make the
uberjar work again if it does not already. It just seemed as though
many did not like it.
Alex
Re: Failed to build the uberjar of ApacheDS
Posted by Stefan Zoerner <sz...@apache.org>.
Alan D. Cabrera wrote:
> On 1/30/2006 2:26 AM, Stefan Zoerner wrote:
>
>> Hi all,
>>
>> I tried to build the uberjar (standalone executyble ApacheDS in a jar)
>> from
>> directory trunks/apacheds via mvn -e assemby:assembly but it fails with
>> message ...
>>
>
> We have this same problem in Geronimo. I think that it's a known bug.
> You have to run that command in the actual assembly directory. Another
> thing, we get a -null.jar at the end of the jar name. Please confirm if
> this is the case for you as well.
>
Thanks Alan,
I was finally able to build it from directory
.../trunks/apacheds/standalone/simple/main
with command
mvn assembly:assembly
But the result has no -null.jar at the end, it is called
org.apache.ldap.server.standalone.simple.main-0.9.4-SNAPSHOT-app.jar
I confess: I do not understand much from m2 configuration, but I assume
this "app" comes from the classifier config in the pom.xml in the
directory mentioned above :
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.1-SNAPSHOT</version>
<configuration>
<archive>
<manifest>
<mainClass>org.apache.ldap.server.ServerMain</mainClass>
</manifest>
</archive>
<descriptor>src/main/assembly/apacheds-main.xml</descriptor>
<classifier>app</classifier>
<appendAssemblyId>false</appendAssemblyId>
</configuration>
</plugin
Probably Alex or Ersin know more about this one.
Greetings, Stefan
Re: Failed to build the uberjar of ApacheDS
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On 1/30/2006 2:26 AM, Stefan Zoerner wrote:
>Hi all,
>
>I tried to build the uberjar (standalone executyble ApacheDS in a jar) from
>directory trunks/apacheds via mvn -e assemby:assembly but it fails with
>message
>
>[INFO] [assembly:assembly]
>[INFO]
>-------------------------------------------------------------------------
>---
>[ERROR] BUILD FAILURE
>[INFO]
>-------------------------------------------------------------------------
>---
>[INFO] No assembly descriptors found.
>[INFO]
>-------------------------------------------------------------------------
>---
>[INFO] Trace
>org.apache.maven.BuildFailureException: No assembly descriptors found. ...
>
>A mvn install runs succesful. I probably make/understand something wrong
>(but what) ...
>Any help is welcome,
> Stefan
>
>I probably have to improve my m2 skills, anyhow :-(
>
>
We have this same problem in Geronimo. I think that it's a known bug.
You have to run that command in the actual assembly directory. Another
thing, we get a -null.jar at the end of the jar name. Please confirm if
this is the case for you as well.
Regards,
Alan
Re: Failed to build the uberjar of ApacheDS
Posted by Ersin Er <er...@gmail.com>.
You may give it a try in apacheds/standalone. We'll document the
installer generation (which Alex makes final touchs) soon.
On 1/30/06, Stefan Zoerner <SZ...@de.ibm.com> wrote:
> Hi all,
>
> I tried to build the uberjar (standalone executyble ApacheDS in a jar) from
> directory trunks/apacheds via mvn -e assemby:assembly but it fails with
> message
>
> [INFO] [assembly:assembly]
> [INFO]
> -------------------------------------------------------------------------
> ---
> [ERROR] BUILD FAILURE
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] No assembly descriptors found.
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Trace
> org.apache.maven.BuildFailureException: No assembly descriptors found. ...
>
> A mvn install runs succesful. I probably make/understand something wrong
> (but what) ...
> Any help is welcome,
> Stefan
>
> I probably have to improve my m2 skills, anyhow :-(
>
>
--
Ersin