p2-repository-plugin problem

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

p2-repository-plugin problem

Lars Fischer
Hello,

I would like to test the p2-repository plugin.

I have a running nexus-oss 1.9.2.4 and activated the contained
capability plugin. This is working fine.

Then I added the p2-repository-plugin and the p2-bridge-plugin but
they are not recognized. They are not listed in the plugin console and
when I try to add a new capability configuration, there is no
selectable capability type (the dropdown field is empty).

The log contains no error or warning about these plugins.

I tried the 1.0-SNAPSHOT, 2.0-SNAPSHOT and 2.0.M3 versions.


What else could I do to get the p2-plugin running?


Regards,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Mirko Swillus
Hej,
Am 27.01.2012 13:32, schrieb Lars Fischer:

> I would like to test the p2-repository plugin.

> I have a running nexus-oss 1.9.2.4 and activated the contained
> capability plugin. This is working fine.

> Then I added the p2-repository-plugin and the p2-bridge-plugin but
> they are not recognized. They are not listed in the plugin console and
> when I try to add a new capability configuration, there is no
> selectable capability type (the dropdown field is empty).

> The log contains no error or warning about these plugins.

Same here (nexus-oss 1.9.2.4). Oldish 1.0-SNAPSHOTs are working
(downloaded on 2011-10-14), new 2.0-M3 versions not. Could someone
please give a hint what versions will go together? This is what I need:

nexus-capabilities-plugin
nexus-p2-bridge-plugin
nexus-p2-repository-plugin

Thanks in advance,
Mirko Swillus

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Brian Demers-2
2.x has not been released yet, but if your looking to use these
artifacts make sure you have a matching Nexus version.  This may not
always be the case, it just happened there have been a few plugins
that also changed to 2.0

So in your case you would want:
nexus oss 2.0-SNAPSHOT
nexus-capabilities-plugin 2.0-SNAPSHOT
nexus-p2-bridge-plugin 2.0-SNAPSHOT
nexus-p2-repository-plugin 2.0-SNAPSHOT



On Tue, Jan 31, 2012 at 3:50 AM, Mirko Swillus <[hidden email]> wrote:

> Hej,
> Am 27.01.2012 13:32, schrieb Lars Fischer:
>
>
>> I would like to test the p2-repository plugin.
>
>
>> I have a running nexus-oss 1.9.2.4 and activated the contained
>> capability plugin. This is working fine.
>
>
>> Then I added the p2-repository-plugin and the p2-bridge-plugin but
>> they are not recognized. They are not listed in the plugin console and
>> when I try to add a new capability configuration, there is no
>> selectable capability type (the dropdown field is empty).
>
>
>> The log contains no error or warning about these plugins.
>
>
> Same here (nexus-oss 1.9.2.4). Oldish 1.0-SNAPSHOTs are working (downloaded
> on 2011-10-14), new 2.0-M3 versions not. Could someone please give a hint
> what versions will go together? This is what I need:
>
> nexus-capabilities-plugin
> nexus-p2-bridge-plugin
> nexus-p2-repository-plugin
>
> Thanks in advance,
> Mirko Swillus
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Lars Fischer
I have got this combination running:
- nexus-oss-webapp-2.0-M4-bundle
- nexus-capabilities-plugin-2.0-SNAPSHOT
- nexus-p2-bridge-plugin-2.0-SNAPSHOT
- nexus-p2-repository-plugin-2.0-SNAPSHOT

But I can not use the published p2 url as source repository for an
eclipse target platform.

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Jason van Zyl
I will be making a bundle that has all the OSGi related plugins working together soon after the 2.0 release. Stay tuned.

On Feb 2, 2012, at 6:25 AM, Lars Fischer wrote:

I have got this combination running:
- nexus-oss-webapp-2.0-M4-bundle
- nexus-capabilities-plugin-2.0-SNAPSHOT
- nexus-p2-bridge-plugin-2.0-SNAPSHOT
- nexus-p2-repository-plugin-2.0-SNAPSHOT

But I can not use the published p2 url as source repository for an
eclipse target platform.

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Simplex sigillum veri. (Simplicity is the seal of truth.)




Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Lars Fischer
Hello Jason,

2012/2/2 Jason van Zyl <[hidden email]>:
> I will be making a bundle that has all the OSGi related plugins working
> together soon after the 2.0 release. Stay tuned.

Good to know.

Thank you,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Manuel Doninger-2
In reply to this post by Jason van Zyl
On Thu, Feb 2, 2012 at 18:35, Jason van Zyl <[hidden email]> wrote:
> I will be making a bundle that has all the OSGi related plugins working
> together soon after the 2.0 release. Stay tuned.

Hello,
i've downloaded the 2.0-Release version of Nexus and the
nexus-capabilities, nexus-p2-bridge and nexus-p2-repository-plugin and
installed them, added the capabilities etc..
If i deploy a maven artifact with an OSGI MANIFEST.MF, the
p2Content.xml and p2Artifacts.xml are created and i can also download
the metadata from http://nexusurl/content/repositories/repo/.meta/p2
(content.jar, artifacts.jar etc.). However, if i add that url to my
Eclipse target platform, it shows no plugins.
Does that feature work for someone? Do i need further configuration to
enable this?

Regards,
Manuel

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Lars Fischer
Hello,

2012/2/15 Manuel Doninger <[hidden email]>:

> i've downloaded the 2.0-Release version of Nexus and the
> nexus-capabilities, nexus-p2-bridge and nexus-p2-repository-plugin and
> installed them, added the capabilities etc..
> If i deploy a maven artifact with an OSGI MANIFEST.MF, the
> p2Content.xml and p2Artifacts.xml are created and i can also download
> the metadata from http://nexusurl/content/repositories/repo/.meta/p2
> (content.jar, artifacts.jar etc.). However, if i add that url to my
> Eclipse target platform, it shows no plugins.
> Does that feature work for someone? Do i need further configuration to
> enable this?

I have tested the public released NexusPro 2.0, already containing the
P2 capabilities.

But I have the same problem:
I added a maven testrepo, created two P2 capabilities and created two
jobs for rebuild the P2 repo/metadata.
Then I deployed some valid OSGi bundles and looked at /testrepo/.meta/p2.
There are artifact.xml and content.xml containing good looking entries.
There are also .jar files inside the /p2/plugins folder. But these
contain only something like "LINK to testrepo:/...".

Trying to use this P2-testrepo inside the Eclipse as source of a
target platform, Eclipse is telling me, that there is no content
available.

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Lars Fischer
Sorry, I did not see that there is also Nexus OSS 2.0 available.
Will try this also.

Regards,
Lars

2012/2/15 Lars Fischer <[hidden email]>:

> Hello,
>
> 2012/2/15 Manuel Doninger <[hidden email]>:
>> i've downloaded the 2.0-Release version of Nexus and the
>> nexus-capabilities, nexus-p2-bridge and nexus-p2-repository-plugin and
>> installed them, added the capabilities etc..
>> If i deploy a maven artifact with an OSGI MANIFEST.MF, the
>> p2Content.xml and p2Artifacts.xml are created and i can also download
>> the metadata from http://nexusurl/content/repositories/repo/.meta/p2
>> (content.jar, artifacts.jar etc.). However, if i add that url to my
>> Eclipse target platform, it shows no plugins.
>> Does that feature work for someone? Do i need further configuration to
>> enable this?
>
> I have tested the public released NexusPro 2.0, already containing the
> P2 capabilities.
>
> But I have the same problem:
> I added a maven testrepo, created two P2 capabilities and created two
> jobs for rebuild the P2 repo/metadata.
> Then I deployed some valid OSGi bundles and looked at /testrepo/.meta/p2.
> There are artifact.xml and content.xml containing good looking entries.
> There are also .jar files inside the /p2/plugins folder. But these
> contain only something like "LINK to testrepo:/...".
>
> Trying to use this P2-testrepo inside the Eclipse as source of a
> target platform, Eclipse is telling me, that there is no content
> available.
>
> Regards,
> Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Mirko Swillus
In reply to this post by Lars Fischer
Hej,
Am 15.02.2012 11:04, schrieb Lars Fischer:

> Trying to use this P2-testrepo inside the Eclipse as source of a
> target platform, Eclipse is telling me, that there is no content
> available.

I'm not sure, but I guess this "Add Software Site" wizard only shows
Features. And since the nexus-p2-repository-plugin only handles Plug-ins
(and not Features), there is nothing to show (nevertheless, be sure to
uncheck "Group by category" at the bottom the wizard page).

But you can edit the .target-File with the text editor, and add your
units (which can be plain bundles) by hand (see the Tycho demo projects
for examples). Afterwards both Tycho and PDE can resolve those artifacts.

The last days I worked on a solution to have (Tycho-build) Features
handled by the nexus-p2-repository-plugin. Using my modified plug-in
within Nexus 2.0.0-SNAPSHOT and Tycho to deploy the artifacts, I see the
deployed features now within the "Add Software Site" wizard as well. If
you are interested in details, drop me a line.

Regards,
Mirko Swillus





____________________________________________________________________

[ M i r k o  S w i l l u s ]

    Software Development

    Qualitype AG
    Quality Management Systems | Bioinformatics
    Moritzburger Weg 67 | 01109 Dresden
    fon +49.351.8838 2813 | fax +49.351.8838 2809
    e-mail: [hidden email] | http://www.qualitype.de

    Sitz der Gesellschaft: Dresden | Amtsgericht Dresden HRB 19830
    Vorstand: Dr. Wilhelm Zörgiebel | Dr. Frank Götz
    Aufsichtsratsvorsitz: Prof. Dr. Gerhard P. Fettweis
____________________________________________________________________

The information in this email and any attachments is confidential and is
intended for the addressee only. If you are not the intended recipient,
please delete this message and any attachments and advise the sender by
return email.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Lars Fischer
Hello Mirko,

2012/2/15 Mirko Swillus <[hidden email]>:
>
> I'm not sure, but I guess this "Add Software Site" wizard only shows
> Features. And since the nexus-p2-repository-plugin only handles Plug-ins
> (and not Features), there is nothing to show (nevertheless, be sure to
> uncheck "Group by category" at the bottom the wizard page).

You are right, the eclipse wizard does not display plain OSGi bundles. My fault.

> But you can edit the .target-File with the text editor, and add your units
> (which can be plain bundles) by hand (see the Tycho demo projects for
> examples). Afterwards both Tycho and PDE can resolve those artifacts.

Thank you for this hint. I will give this a try.

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Manuel Doninger-2
In reply to this post by Mirko Swillus
Hi Mirko,

On Wed, Feb 15, 2012 at 12:11, Mirko Swillus <[hidden email]> wrote:
> Hej,

...

> The last days I worked on a solution to have (Tycho-build) Features handled
> by the nexus-p2-repository-plugin. Using my modified plug-in within Nexus
> 2.0.0-SNAPSHOT and Tycho to deploy the artifacts, I see the deployed
> features now within the "Add Software Site" wizard as well. If you are
> interested in details, drop me a line.

is your code somewhere accessible in a Github repository? It would be
great to test your modifications, since we're currently evaluating the
p2 functionalities of Nexus for a new project.


> Regards,
> Mirko Swillus

Regards,
Manuel

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Lars Fischer
In reply to this post by Lars Fischer
2012/2/15 Lars Fischer <[hidden email]>:
>> But you can edit the .target-File with the text editor, and add your units
>> (which can be plain bundles) by hand (see the Tycho demo projects for
>> examples). Afterwards both Tycho and PDE can resolve those artifacts.
>
> Thank you for this hint. I will give this a try.

I edited the .target file and inserted a unit conained inside the
nexus P2 repository.
Now eclipse is able to retrieve this bundle.

But the generated OSGi metadata is defect: I deployed an OSGi bundle
with a correct "Import-Package:" entry.
The bundle delivered back to eclipse is missing this entry. Instead,
there are many, many additional entries about the server hosting the
nexus inside the MANIFEST.MF:

CATALINA_OPTS: -Djava.awt.headless=true -Dorg.apache.jasper.runtime.Body
 ContentImpl.LIMIT_BUFFER=true -XX:MaxPermSize=256m -Xms512m -Xmx768m
COLORTERM: 1
CPU: x86_64
Created-By: Apache Maven Bundle Plugin
CSHEDIT: emacs
CVS_RSH: ssh
Embed-Dependency: *;scope=compile|runtime;inline=true
ENV: /etc/bash.bashrc
EXECUTOR_NUMBER: 0
G_BROKEN_FILENAMES: 1
HISTCONTROL: ignoreboth
HISTSIZE: 1000
HOSTTYPE: x86_64
INFODIR: /usr/local/info:/usr/share/info:/usr/info
INFOPATH: /usr/local/info:/usr/share/info:/usr/info
INPUTRC: /etc/inputrc
IS_M2RELEASEBUILD: false
LANG: POSIX
LC_CTYPE: en_US.UTF-8
LD_LIBRARY_PATH: /usr/java/jdk1.6.0_20/jre/lib/amd64/server:/usr/java/jd
 k1.6.0_20/jre/lib/amd64:/usr/java/jdk1.6.0_20/jre/../lib/amd64
LESS: -M -I
LESS_ADVANCED_PREPROCESSOR: no
LESSCLOSE: lessclose.sh %s %s
LESSKEY: /etc/lesskey.bin
LESSOPEN: lessopen.sh %s
LS_COLORS: no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=4
 0;33;01:cd=40;33;01:or=41;33;01:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=
 01;32:*.bat=01;32:*.btm=01;32:*.dll=01;32:*.tar=00;31:*.tbz=00;31:*.tgz
 =00;31:*.rpm=00;31:*.deb=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.lz
 ma=00;31:*.zip=00;31:*.zoo=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=0
 0;31:*.tb2=00;31:*.tz2=00;31:*.tbz2=00;31:*.avi=01;35:*.bmp=01;35:*.fli
 =01;35:*.gif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mng=01;35:*.mov=01;35:*.m
 pg=01;35:*.pcx=01;35:*.pbm=01;35:*.pgm=01;35:*.png=01;35:*.ppm=01;35:*.
 tga=01;35:*.tif=01;35:*.xbm=01;35:*.xpm=01;35:*.dl=01;35:*.gl=01;35:*.w
 mv=01;35:*.aiff=00;32:*.au=00;32:*.mid=00;32:*.mp3=00;32:*.ogg=00;32:*.
 voc=00;32:*.wav=00;32:
LS_OPTIONS: -A -N --color=tty -T 0
MACHTYPE: x86_64-suse-linux
MAIL: /var/mail/root
MANPATH: /usr/share/man:/usr/local/man
MAVEN_OPTS: -Xmx768m -XX:MaxPermSize=512m
MC_SID: 32555
MC_TMPDIR: /tmp/mc-root
MINICOM: -c on
MORE: -sl
NLSPATH: /usr/dt/lib/nls/msg/%L/%N.cat
NNTPSERVER: news
NODE_LABELS: master
NODE_NAME: master
OSTYPE: linux
PAGER: less
PATH: /sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:
 /bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/usr/lib/mit/
 bin:/usr/lib/mit/sbin
PLEXUS_NEXUS_WORK: /data/nexus_home
PROFILEREAD: true
PYTHONSTARTUP: /etc/pythonstart
QT_HOME_DIR: /usr/share/desktop-data
SHELL: /bin/bash
SHLVL: 4
SSH_TTY: /dev/pts/1
SVN_REVISION: 8756
TERM: xterm
Tool: Bnd-1.50.0
XCURSOR_THEME: DMZ
XDG_CONFIG_DIRS: /etc/xdg
XDG_DATA_DIRS: /usr/share:/etc/opt/kde3/share:/opt/kde3/share
XFILESEARCHPATH: /usr/dt/app-defaults/%L/Dt
XKEYSYMDB: /usr/share/X11/XKeysymDB
XNLSPATH: /usr/share/X11/nls
[...]


This can't be right.
Where is my mistake?

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Stuart McCulloch-2
On 16 Feb 2012, at 08:38, Lars Fischer <[hidden email]> wrote:

> 2012/2/15 Lars Fischer <[hidden email]>:
>>> But you can edit the .target-File with the text editor, and add your units
>>> (which can be plain bundles) by hand (see the Tycho demo projects for
>>> examples). Afterwards both Tycho and PDE can resolve those artifacts.
>>
>> Thank you for this hint. I will give this a try.
>
> I edited the .target file and inserted a unit conained inside the
> nexus P2 repository.
> Now eclipse is able to retrieve this bundle.
>
> But the generated OSGi metadata is defect: I deployed an OSGi bundle
> with a correct "Import-Package:" entry.
> The bundle delivered back to eclipse is missing this entry. Instead,
> there are many, many additional entries about the server hosting the
> nexus inside the MANIFEST.MF:

Did you build this bundle with maven-bundle-plugin 2.3.5/2.3.6? If so then it could be due to https://issues.apache.org/jira/browse/FELIX-3347 - updating your pom.xml to maven-bundle-plugin 2.3.7 and rebuilding & redeploying the bundle should fix this.

--
Cheers, Stuart

> CATALINA_OPTS: -Djava.awt.headless=true -Dorg.apache.jasper.runtime.Body
> ContentImpl.LIMIT_BUFFER=true -XX:MaxPermSize=256m -Xms512m -Xmx768m
> COLORTERM: 1
> CPU: x86_64
> Created-By: Apache Maven Bundle Plugin
> CSHEDIT: emacs
> CVS_RSH: ssh
> Embed-Dependency: *;scope=compile|runtime;inline=true
> ENV: /etc/bash.bashrc
> EXECUTOR_NUMBER: 0
> G_BROKEN_FILENAMES: 1
> HISTCONTROL: ignoreboth
> HISTSIZE: 1000
> HOSTTYPE: x86_64
> INFODIR: /usr/local/info:/usr/share/info:/usr/info
> INFOPATH: /usr/local/info:/usr/share/info:/usr/info
> INPUTRC: /etc/inputrc
> IS_M2RELEASEBUILD: false
> LANG: POSIX
> LC_CTYPE: en_US.UTF-8
> LD_LIBRARY_PATH: /usr/java/jdk1.6.0_20/jre/lib/amd64/server:/usr/java/jd
> k1.6.0_20/jre/lib/amd64:/usr/java/jdk1.6.0_20/jre/../lib/amd64
> LESS: -M -I
> LESS_ADVANCED_PREPROCESSOR: no
> LESSCLOSE: lessclose.sh %s %s
> LESSKEY: /etc/lesskey.bin
> LESSOPEN: lessopen.sh %s
> LS_COLORS: no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=4
> 0;33;01:cd=40;33;01:or=41;33;01:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=
> 01;32:*.bat=01;32:*.btm=01;32:*.dll=01;32:*.tar=00;31:*.tbz=00;31:*.tgz
> =00;31:*.rpm=00;31:*.deb=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.lz
> ma=00;31:*.zip=00;31:*.zoo=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=0
> 0;31:*.tb2=00;31:*.tz2=00;31:*.tbz2=00;31:*.avi=01;35:*.bmp=01;35:*.fli
> =01;35:*.gif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mng=01;35:*.mov=01;35:*.m
> pg=01;35:*.pcx=01;35:*.pbm=01;35:*.pgm=01;35:*.png=01;35:*.ppm=01;35:*.
> tga=01;35:*.tif=01;35:*.xbm=01;35:*.xpm=01;35:*.dl=01;35:*.gl=01;35:*.w
> mv=01;35:*.aiff=00;32:*.au=00;32:*.mid=00;32:*.mp3=00;32:*.ogg=00;32:*.
> voc=00;32:*.wav=00;32:
> LS_OPTIONS: -A -N --color=tty -T 0
> MACHTYPE: x86_64-suse-linux
> MAIL: /var/mail/root
> MANPATH: /usr/share/man:/usr/local/man
> MAVEN_OPTS: -Xmx768m -XX:MaxPermSize=512m
> MC_SID: 32555
> MC_TMPDIR: /tmp/mc-root
> MINICOM: -c on
> MORE: -sl
> NLSPATH: /usr/dt/lib/nls/msg/%L/%N.cat
> NNTPSERVER: news
> NODE_LABELS: master
> NODE_NAME: master
> OSTYPE: linux
> PAGER: less
> PATH: /sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:
> /bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/usr/lib/mit/
> bin:/usr/lib/mit/sbin
> PLEXUS_NEXUS_WORK: /data/nexus_home
> PROFILEREAD: true
> PYTHONSTARTUP: /etc/pythonstart
> QT_HOME_DIR: /usr/share/desktop-data
> SHELL: /bin/bash
> SHLVL: 4
> SSH_TTY: /dev/pts/1
> SVN_REVISION: 8756
> TERM: xterm
> Tool: Bnd-1.50.0
> XCURSOR_THEME: DMZ
> XDG_CONFIG_DIRS: /etc/xdg
> XDG_DATA_DIRS: /usr/share:/etc/opt/kde3/share:/opt/kde3/share
> XFILESEARCHPATH: /usr/dt/app-defaults/%L/Dt
> XKEYSYMDB: /usr/share/X11/XKeysymDB
> XNLSPATH: /usr/share/X11/nls
> [...]
>
>
> This can't be right.
> Where is my mistake?
>
> Regards,
> Lars
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Lars Fischer
Hello Stuart,

2012/2/16 Stuart McCulloch <[hidden email]>:

> Did you build this bundle with maven-bundle-plugin 2.3.5/2.3.6?
> If so then it could be due to https://issues.apache.org/jira/browse/FELIX-3347
> - updating your pom.xml to maven-bundle-plugin 2.3.7 and rebuilding &
> redeploying the bundle should fix this.

Great, this was the reason. Upgrading fixed it.

OT: Is there a way to tell eclipse to clean the cached bundle pool of
a target platform without deleting by hand and restarting eclipse?
The reload button has no effect.

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Lars Fischer
2012/2/16 Lars Fischer <[hidden email]>:
>
> OT: Is there a way to tell eclipse to clean the cached bundle pool of
> a target platform without deleting by hand and restarting eclipse?
> The reload button has no effect.

Deploying a new SNAPSHOT version of a bundle does not change the P2
repository artifacts.xml artifact properties.

E.g. "repositoryPath" stays pointing at the SNAPSHOT-timestamp"-1",
although there are more new SNAPSHOT versions inside the Maven
Repository.
I tried to run the "Rebuild P2 Metadata" and "Rebuild P2 Repository"
tasks. They are touching the artifacts.xml file, but the properties do
not change. So Eclipse gets no chance to reload the new content.

Additional: if I clean the local eclipse bundle pool to force a new
download. The latest file of the SNAPSHOT version is delivered. But it
does not match the old md5 check sum contained in the artifacts.xml.
Now eclipse prevents to load the latest SNAPSHOT version because of a
wrong md5 and I'm no longer able to use this P2 repository.

A workaround is to completely delete the nexus .meta/P2/ folder and
rerun the nexus P2 tasks.

Is this the expected behavior or a bug?


Regards,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Lars Fischer
2012/2/16 Lars Fischer <[hidden email]>:
>
> Deploying a new SNAPSHOT version of a bundle does not change the P2
> repository artifacts.xml artifact properties.
>
> A workaround is to completely delete the nexus .meta/P2/ folder and
> rerun the nexus P2 tasks.

I changed the creation of new SNAPSHOT bundles to use a unique
.qualifier version setting for the Bundle-Version manifest entry. Now
nexus recognizes new SNAPSHOT bundles also as new P2 artifacts.

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: p2-repository-plugin problem

Mirko Swillus
In reply to this post by Manuel Doninger-2
Hej Manuel and Lars,
Am 15.02.2012 16:15, schrieb Manuel Doninger:

> On Wed, Feb 15, 2012 at 12:11, Mirko Swillus<[hidden email]>  wrote:
>> The last days I worked on a solution to have (Tycho-build) Features handled
>> by the nexus-p2-repository-plugin. Using my modified plug-in within Nexus
>> 2.0.0-SNAPSHOT and Tycho to deploy the artifacts, I see the deployed
>> features now within the "Add Software Site" wizard as well. If you are
>> interested in details, drop me a line.

> is your code somewhere accessible in a Github repository? It would be
> great to test your modifications, since we're currently evaluating the
> p2 functionalities of Nexus for a new project.

I created a fork and pushed my modifications to it. It is highly
untested and hackish, can surely be optimized and will only work if you
build your bundles and features with Tycho. It does not work for
artifacts of classifier "binary".

Here is the URL:
[hidden email]:mechko/nexus-p2-repository-plugin.git

Build the jar (unfortunately the tests do not happen, but the jar is
materialized correctly). Install the nexus-p2-bridge-plugin and
nexus-capabilities-plugin (both in version 2.0) and the
nexus-p2-repository-plugin in version 2.1-SNAPSHOT (get the bundled
version from repository.sonatype.org) to the plugin-repository. Than
replace the jar in the nexus-p2-repository-plugin with the one you build
(it defines its dependencies to the 2.0 versions).

The nexus-p2-repository-plugin basically provides two features: A
p2-Metadata Generator, which is not touched by this patch, and a
p2-Metadata Aggregator. I modified this Aggretator to use the metadata
that is already there from the Tycho build (and not the ones from the
Generator, so you don't need to run the Generator-Task). This was
possible because the xml filenames are slightly diffrent:

The Nexus Plug-In generates

{artifactId}p2Artifacts.xml and {artifactId}p2Content.xml

Tycho is uploading this ones

{artifactId}p2artifacts.xml and {artifactId}p2metadata.xml

Unfortunately, the files generated by Tycho do not frame their content
in a proper <repository> header, and so the p2 runtime called by the
plug-in refuses to do the merge job. So I had to add the missing lines
to both files before merging.

Afterwards I had to find a new approach to create the links from the
/plugins and /features to the physical jars. This was quite difficult
and the solution I found is pretty hackish (but works for me).

Thats it. Additionally, I had to adjust some dependencies within the
pom.xml, otherwise the plug-in wont compile (see the thread on this
list). Regards,

Mirko Swillus





---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]