Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to Pax stack? #2

Open
tonit opened this issue Jan 9, 2014 · 4 comments
Open

Move to Pax stack? #2

tonit opened this issue Jan 9, 2014 · 4 comments

Comments

@tonit
Copy link
Member

tonit commented Jan 9, 2014

Just a guess, how about pushing this to the Pax stack (rename git project org.ops4j.pax.peaberry) and general naming Pax Peaberry (or PP for short). WDYT?

@tonit
Copy link
Member Author

tonit commented Jan 9, 2014

Alternatively, to be discussed with Stuart maybe, rename it to Pax DI, Pax Inject or Pax Guice.

@mcculls
Copy link
Member

mcculls commented Jan 9, 2014

No objections to renaming the git project name to org.ops4j.pax.peaberry. Wrt. general naming: Pax DI could be confused with Pax CDI, and Pax Guice sounds like a fork of Guice, but Pax Inject might work (though then there's a disconnect between the project name and the packages/symbolic names).

@niclash
Copy link
Member

niclash commented Jan 9, 2014

Keep the funky name... ;-)
On Jan 9, 2014 8:56 PM, "Stuart McCulloch" notifications@github.com wrote:

No objections to renaming the git project name to org.ops4j.pax.peaberry.
Wrt. general naming: Pax DI could be confused with Pax CDI, and Pax Guice
sounds like a fork of Guice, but Pax Inject might work (though then there's
a disconnect between the project name and the packages/symbolic names).


Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-31928159
.

@tonit
Copy link
Member Author

tonit commented Jan 9, 2014

@niclash Keep the funky red hair.. ;)

You are right Stuart with "Pax Inject" being the only real alternative. Niclas you are right that this does not beat the Peaberry name.

Background from my side: I stumbled over peaberry again as i was following Guices' remainings (very few info on whats behind the mysterious 4.0beta).
Somehow i missed the import of peaberry into ops4j last year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants