RE: [mevenide-user] problem with profile activation
"Mohni, Daniel" <[email protected]>
| Newsgroups | gmane.comp.jakarta.turbine.maven.mevenide.user |
|---|---|
| Message-ID | <B91E33CF995E4F46811E25CD877F384C028E5F88@GBMK-EXCH3.eu.uis.unisys.com> |
Hi Milos, I just thinked about it, and now I moved the build part of my profile outside of profiles, I was just copy pasting your created code, and didn't think any further. So this is not an issue, as you also mentioned profiles should be activated when used, maybe in the continuum build and not in the development build... Anyway it's realy amazing how the integration with netbeans work, when I look at the trubles my co-workers have with eclipse ;-) tnx Daniel ________________________________ From: Milos Kleint [mailto:[email protected]] Sent: Thursday, November 08, 2007 1:08 PM To: [email protected] Subject: Re: [mevenide-user] problem with profile activation "Active by default" means the profile is activated when no other profile is activated. In netbeans The netbeans-public and netbeans-private profiles are always dynamically added as activated from the IDE. http://www.netbeans.org/issues/show_bug.cgi?id=97808 shall be adressing this in some future releases. I haven't done a full-scale review but the profiles are only required at a few places 1. to add an additional remote repository (file:// based one) that points to the location with netbeans specific plugins that are used for deployment/running jars etc. The idea behind this is to allow people who can't access the central repo to use these plugins. 2. have the build of jar trigger the assembly plugin processing once user sets the main class and everything, as the "Run project" action depends on it. 3. anything that gets written in profiles.xml needs to be included in a profile that is to be activated. to rectify the automatic profile activation, I'll need to find a solution to these points. re. descriptor vs. descriptors: I know about it, just don't feel like forcing it on people. when updating the profile, I don't set the version currently which means the latest is used, however if someone explicitly sets it to a certain version I don't want to break it in case it's a version not supporting descriptors element. In any case probably worth filing as issue, so that it's not forgotten and gets ultimately replaced by the non-deprecated value. Regards Milos On 11/7/07, Mohni, Daniel <[email protected]> wrote: Hi, I use a profile like the one generated by mevenide to build an assembly for my project. I want that this profile is active by default using <activeByDefault> option... in the pom I added this: <profile> <id>distribution-build</id> <activation> <activeByDefault>true</activeByDefault> </activation> <build> <plugins> <plugin> <artifactId>maven-jar-plugin</artifactId> <configuration> <archive> <manifest> <addClasspath>true</addClasspath> <classpathPrefix>lib</classpathPrefix> <mainClass>Startup</mainClass> </manifest> </archive> </configuration> </plugin> <plugin> <artifactId>maven-assembly-plugin</artifactId> <executions> <execution> <id>dist</id> <phase>install</phase> <goals> <goal>assembly</goal> </goals> <configuration> <descriptors> <descriptor>${basedir}/src/main/assemblies/service.xml</descriptor> </descriptors> <finalName>${project.artifactId}</finalName> </configuration> </execution> </executions> </plugin> </plugins> </build> </profile> this profile will be active if I start maven from the commandline but not if I build the project inside Netbeans6.0b2. I just want to let you know..... for Milos: <configuration> <descriptor>${basedir}/src/main/assemblies/netbeans-run.xml</descriptor> <finalName>executable</finalName> </configuration> I got a warning with assebly-plugin version 2.2 beta 1 that <descriptor> is now deprecated, and to use <descriptors> <configuration> <descriptors> <descriptor>${basedir}/src/main/assemblies/netbeans-run.xml</descriptor> </descriptors> <finalName>executable</finalName> </configuration> --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email